> Production API availability: use /api/v1/help?view=guides and the resource operations catalog before following a recipe. Some localhost capabilities are not deployed yet; an absent operation is unavailable.
Inspect the saved shape
A board is configuration, not a place to paste an entire application. The example below is a structural excerpt. It omits template-specific CSS, deployment settings and other required fields; do not POST it as a complete board.
{
"menu": {
"guide_intro": {
"header": { "h1": "Build one section at a time" }
}
},
"list": [
{
"listname": "Guide",
"module": "home",
"component": "frontend",
"type": "Frontend",
"controller": "Guides",
"action": "overview",
"page_settings": {
"General": { "page_title": "Guide", "url_slug": "/guide" },
"route": "/guide"
},
"datalist": [
{
"section_id": "guide-intro",
"name": "Guide introduction",
"data_mapping": {
"intro": {
"0": ["header"],
"1": ["databoard", "menu", "guide_intro", "header"]
}
}
}
]
}
]
}The section also needs a registered template, its parameters file and the matching CSS configuration. Read those from an existing compatible section or the template registry. Field names are a contract; inventing a plausible template name does not create a renderer.
Preserve identity
Use the page route and a stable section_id to target a patch. A heading is display text, not a reliable identity. Keep the existing section ID when revising it.
The HMVC component type is Frontend for these public pages. The component path is frontend, while home is the module name. Mixing these fields can generate a controller into the wrong directory even if the JSON parses.
Keep the action consistent
The page and HMVC configuration must agree on module, controller and action. Choose a simple alphanumeric action name such as overview; the public route can still be /getting-started. URL spelling and PHP action naming are separate concerns.
For a new page, use ensure_hmvc_action, ensure_page and set_route through a patch. For an existing heading, update only its owning menu field. Do not rebuild the HMVC structure to change copy.
Inspect the template registry
Repository references: app/antsand_bootstrap/project/common_views/parameter_files.json and outline2design.json. The registry provides the renderer path, template identifier and CSS field schema.
Use patches for changes and validation before generation.