> 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.
Content records
Notes owns articles. Forms owns form definitions and workflow configuration. Docs owns these chapters and their published state. A page should reference those records through a mapping when the module is the source of truth.
Changing the same content in both a module and a copied page creates competing versions. Inspect the mapping before deciding what to edit.
Groups and websites
Groups associate content with its intended use. A website and alias identify a deployment target. A Databoard supplies the configuration for that target.
Group membership alone is not a universal authorization rule. Each module and endpoint must enforce its own owner and access checks.
Header, body and footer
Use the section header for its introduction, the body for its repeating content or module renderer, and the footer for a closing action or supporting detail.
Use structured fields for headings, paragraphs, links and facts. Upload a diagram as an asset and map its URL. Add a shared renderer only when the existing structured fields cannot express the component.
Application structure
HMVC describes modules, controllers, actions and their access rules. The visible page and the action a form submits to are different parts of the same flow.
A page can render correctly while its submit action is missing. Inspect both the presentation mapping and the route and permission definitions before treating the flow as complete.
Generated files
Treat generated files as release output. Editing them directly loses the source connection and can be overwritten by regeneration. Fix the content record, section configuration, shared template or generator that owns the behavior.
Trace the flow over HTTP
- GET /api/v1/me establishes the key identity and scopes.
- GET /api/v1/groups discovers accessible group associations.
- GET /api/v1/databoards and GET /api/v1/databoards/{id} identify the owned board and saved bindings.
- GET /api/v1/databoards/{id}/page-flow traces routes, sections and mapped sources.
- Read the owning module through its documented resource endpoint before editing its data.
- Validate the intended change, save it, read it back and generate the explicit target when required.
Groups provide shared association across modules; they do not copy every record into Databoard. Databoard maps selected sources into templates and HMVC pages. Generated sites then serve the projected content and may retain their own SQLite member, purchase or submission data. Central delivery of an email does not move ownership of a site-local password or purchase record into the central Forms module.
The exact group rule depends on the endpoint. A group association cannot expand an API key's scope or bypass record ownership. Inspect Forms diagnostics for submission destinations and workflow execution instead of assuming every form stores data centrally.