Get started with POM Theme
POM Theme combines a visual Page Builder with shared design and layout settings, structured content, dynamic HTML templates, forms, faceted search, WooCommerce presentation, integrations, and supported developer extension points.
This chapter takes you from an installable package to a representative site review and, later, a production launch decision.

Choose the article for your next decision
| If you need to… | Read |
|---|---|
| Install the private theme package or update an existing site | Install and update POM Theme |
| Connect a domain, understand plan capacity, or configure multisite licensing | Connect the POM Theme license |
| See the principal settings and editing areas in context | Tour a POM Theme site |
| Decide whether a value belongs to WordPress, the builder, Theme settings, a content model, or a template | Understand what owns each part of a POM site |
| Locate a specific administration screen | Find the major POM Theme interfaces |
| Follow the shortest route for your role or project | Choose your learning path |
| Produce one representative page before scaling the build | Configure and review your first POM site |
| See how all thirteen documentation chapters fit together | Complete documentation map |
| Approve a finished site for production | Review a POM Theme site before launch |
| Connect Analytics, Ads, or a Tag Manager container | Set up Google tags and Tag Manager |
Recommended first week with a new site
- Confirm the server and WordPress installation can run the current POM release.
- Install POM on a recoverable staging site.
- Validate the license for the correct domain or multisite network.
- Tour the settings without enabling optional systems.
- Decide which layer owns each requirement.
- Establish the initial design system and persistent site layout.
- Build one representative page with real content.
- Add structured content, templates, forms, search, integrations, or commerce only where the project requires them.
- Review the representative page across roles, devices, and failure states before expanding the build.
The production launch checklist belongs at the end of the project, not at the end of installation.
The central editing rule
Edit the owner of the decision:
- change a title or price in the WordPress or WooCommerce record;
- change one page's composition in the POM Page Builder;
- change a shared brand or layout choice under Settings → POM Theme;
- change the site's data structure under Content model;
- change repeated archive, feed, or single presentation through its template.
This rule prevents local overrides and repeated fixes from hiding a global configuration problem.
Safe working habits
- Work on staging for structural changes.
- Use real-length content early.
- Enable only required optional systems.
- Save and re-open settings when enabling a feature reveals additional fields.
- Verify signed-out and authenticated behavior separately.
- Check mobile layout and keyboard use before duplicating a page pattern.
- Confirm source configuration before clearing generated output or caches.
- Never include passwords, license keys, authentication cookies, or customer data in documentation or support evidence.
Chapter contents
- Install and update POM Theme
- Connect the POM Theme license
- Tour a POM Theme site from settings to frontend
- Understand what owns each part of a POM site
- Find the major POM Theme interfaces
- Choose your POM Theme learning path
- Configure and review your first POM site
- Complete POM Theme documentation map
- Review a POM Theme site before launch