pom://site/builder: compose POM classic builder content

This Markdown resource explains the operational rules for pages whose content is stored as nested POM and Visual Composer-style shortcodes.

Structural contract

The basic hierarchy is:

[vc_row]
    [vc_column]
        [web_title]A clear heading[/web_title]
        [vc_column_text]Supporting copy.[/vc_column_text]
    [/vc_column]
[/vc_row]

Use vc_row and vc_column for the outer grid. Inner layouts use their corresponding inner row and column tags. POM modules such as web_* sit inside a permitted content container. Container modules must keep their documented children; a visually plausible but structurally invalid nesting can disappear or render incorrectly in the builder.

The resource’s workflow

The guide directs a client to:

1. inspect authoring context;
2. list available shortcodes;
3. read the schema for each selected tag;
4. generate one complete shortcode tree;
5. validate it with pom_validate_builder_content;
6. repair every error before creating or updating the page.

Prefer component attributes for spacing, alignment, color, imagery, and responsive behavior when the live schema exposes them. Raw grids, scripts, and ad hoc CSS are poor substitutes for a supported module setting and may not survive future editing.

Existing pages

Read the current page before editing it. Preserve its row/column nesting, shortcode IDs, meaningful classes, merge tags, and unrelated sections. Validate the full proposed content because a replacement fragment can unbalance an opening or closing tag elsewhere.

The guide does not make a write. Use wp_create_page or wp_update_page only after the target, status, and final markup are confirmed.

Related guides: layout guide, shortcode catalog, and update a builder page without flattening it.