Complete POM Theme documentation map
Use this map when a task crosses several areas or when you know the outcome but not the WordPress screen that owns it.
Start and operate the theme
| Chapter | Use it for |
|---|---|
| Start here | Installation, licensing, orientation, the first representative site review, and launch preparation. |
| POM Theme help | Symptom-led diagnosis and the information needed for a safe support request. |
Build the site
| Chapter | Use it for |
|---|---|
| Page Builder | Page-specific rows, columns, components, responsive controls, reusable content, media, maps, and builder troubleshooting. |
| Design system | Brand assets, palette, fonts, buttons, icons, global styles, and shared component appearance. |
| Site layout | Header, navigation, subheader, breadcrumbs, footer, contact dock, sidebars, and persistent site structure. |
| Content models | Post types, taxonomies, custom fields, saved queries, permission rules, and content-model planning. |
| Forms | Form activation, creation, placement, submissions, notifications, uploads, storage, privacy, and integrations. |
| Faceted search | Indexed filtering, search contexts, facets, gateways, maps, result listings, and native search. |
| Dynamic templates | Archive, feed, and single HTML templates, assignments, merge tags, blog views, and reusable presentation. |
Look up a specific interface
| Chapter | Use it for |
|---|---|
| Shortcode library | The visible controls, attributes, requirements, and output of individual POM builder components. |
| WooCommerce | POM storefront presentation and optional shop, product, cart, checkout, account, shipping, and promotion enhancements. |
| Developer reference | Stable public extension contracts, programmatic registration, assets, security expectations, and supported CLI commands. |
Follow a complete outcome
Recipes join several chapters into end-to-end projects. Use them after understanding the ownership boundaries involved in the project; a recipe links to the focused reference instead of repeating it.
Common cross-chapter routes
A brochure or service site
A directory or searchable catalog
A WooCommerce store
- WooCommerce
- Design system
- Site layout
- Forms, if the store uses POM forms
- Help, for launch-blocking symptoms
A custom integration
- Read the user-facing chapter for the feature.
- Confirm the supported public behavior.
- Continue with the matching developer reference.
- Verify the complete visitor or editor workflow, not only the hook callback.
Prepare a safe support request
If none of the symptom guides resolves the problem, record the affected URL, WordPress and PHP versions, user role, device, exact action, expected result, actual result, and the last relevant change.
Share reproducible and sanitized evidence. Never include passwords, license keys, authentication cookies, customer data, or unrestricted exports.