Page Builder overview

POM Page Builder stores a page as a hierarchy of shortcodes: rows contain columns, and columns contain the components visitors see. The editor represents that hierarchy visually so content editors do not need to write the shortcode markup.

What belongs in Page Builder

Use the builder for decisions that belong to one page:

• the sequence of its sections;
• the number and proportions of columns;
• headings, copy, images, buttons, forms, maps, and listings;
• a local background, spacing, alignment, or visibility choice;
• a page-specific CSS class when a supported setting is not enough.

Use Settings → POM Theme for site-wide decisions such as typography, colors, shared navigation, integrations, and other global behavior. If the same local override appears on many pages, make it a shared design decision instead of repeating it.

The content hierarchy

Page
└── Row
    ├── Column
    │   ├── Title
    │   ├── Text Block
    │   └── Button
    └── Column
        └── Image

A normal component must be inside a column. Container components such as tabs, accordions, maps, and carousels accept only their own compatible child items.

Two editing views

The Backend Editor emphasizes structure and is the safest choice for moving or reorganizing sections. The Frontend Editor lets authorized users work against a visual rendering of the page. Both edit the same saved content; choose the view that makes the current task easiest.

See Choose between the Backend Editor and Frontend Editor.

What saving means

Builder changes are part of the WordPress post. The action available to you may be Publish, Update, or Submit for Review, depending on the post status and your role. Preview is a review step, not proof that the public URL has been updated.

A maintainable page

A maintainable page uses:

• one row for each meaningful section;
• the shallowest column structure that meets the design;
• a logical source order that also works when columns stack;
• global styles before one-off overrides;
• reusable blocks for content that must remain synchronized;
• descriptive labels and unique manual identifiers.

Continue with Build your first page for a complete first workflow.