Tour a POM Theme site from settings to frontend

This walkthrough follows one visible page through the POM Theme interfaces that can influence it. Use it after installation when you want to understand the product before configuring a complete project.

POM Theme uses Settings → POM Theme instead of the WordPress Customizer for its current shared settings.

Begin with one published page

Choose a simple public page with:

• a title;
• body copy;
• one image;
• one button or link;
• a place in the main menu.

Open it in a signed-out browser window and keep that URL available. The walkthrough will distinguish the content record, the page composition, and the shared frame around it.

1. Identify the content record

Open the page in the normal WordPress editor.

The record owns its title, status, featured image, author, terms, and other WordPress data. When Page Builder access is enabled for the role and post type, the same screen also exposes the composed rows, columns, and components stored for that page.

Change a harmless piece of page copy, update the page, and confirm only that page's content changes. Revert the copy if the walkthrough is running on an established site.

2. Inspect the design system

Open Settings → POM Theme → Design system.

Visit:

• Theme preview
• Brand
• Color palette
• Fonts
• Buttons
• General styles

These are shared decisions. A palette or button change can affect many theme and builder outputs, so inspect rather than save a change unless the site owner has approved it.

3. Follow the persistent frame

Open Settings → POM Theme → Site layout and compare the configured Header, Mobile navigation, Subheader, Breadcrumbs, and Footer with the public page.

Then open Appearance → Menus → Manage Locations. Theme settings decide which header structures are active; WordPress menu locations decide which menu is inserted into them.

This explains a common mismatch: changing a menu assignment cannot change the selected header layout, and changing the header layout does not create or populate a WordPress menu.

4. Find the template layer

Open Settings → POM Theme → Templates.

The page chosen for this tour may use its ordinary Page Builder content, but archives, feeds, single records, search results, the blog, authors, and eligible custom post types can use shared template settings or POM HTML templates.

Open one archive or single view used by the site and ask:

• Which content record supplies the values?
• Which template decides their repeated arrangement?
• Which Site layout settings wrap the result?
• Which Design system values style it?

Do not edit a template to correct one bad content value.

5. See how optional systems appear

Return to the main POM Theme settings tabs:

• Content model adds structured content, fields, queries, search contexts, and permission rules.
• Forms activates and styles the POM forms system; individual forms then live under the separate Forms menu.
• E-Commerce configures POM's WooCommerce presentation and optional enhancements.
• Integrations connects supported external services.
• Advanced contains code, performance, and compatibility controls intended for administrators.

Many optional settings have an enable control. Their configuration or dependent interface can appear only after the setting is enabled and saved.

6. Observe local overrides

Return to the chosen page's editor and inspect its POM-specific settings. Individual content can override selected global header, subheader, breadcrumb, footer, stylesheet, script, template, or critical-CSS behavior where those controls are provided.

If the public page differs from the global theme setting, check the content-level override before changing the global value for the whole site.

7. Review the frontend deliberately

Open the page:

1. Signed out at a desktop width.
2. Signed out at a mobile width.
3. Signed in as the intended editor.
4. With keyboard navigation.

Identify which layer owns each visible part. Confirm that mobile navigation is usable, the heading order is understandable, the image has appropriate alternative text, and the primary action has a clear focus state.

What you should know after the tour

You have completed the walkthrough when you can answer:

• Where is the information stored?
• Is its arrangement unique to one page or shared by a template?
• Is its appearance inherited from the Design system?
• Does the Site layout own the surrounding structure?
• Is a local content override changing the global result?
• Is an optional feature or integration required?

Next, use Choose your POM Theme learning path or begin the first-site checklist.