How Databoard works — Antsand Docs

> 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.

Read the system in three parts

Databoard connects an application contract to content and a presentation. Start by identifying each part before editing JSON.

Content modules own records: Notes owns articles, Docs owns chapters, Forms owns form configuration, and Ecommerce owns catalog records.
HMVC describes modules, controllers, actions, routes and access rules.
A page contains sections. Each section selects a template and maps source data into that template's fields.

Exampletext

Docs collection / Notes / Forms / catalog
                  |
             source projection
                  |
Databoard page -> section mapping -> template header / body / footer
                  |
HMVC route -> controller -> view -> generated website

The mapping is a useful architecture check. If the content can only appear because a generated view was edited by hand, the factory does not own that result yet.

What belongs where

Keep chapter prose in Docs. Keep a shared navigation structure in the board's menu configuration. Keep site typography and reusable component styles in Sass v2 and the site's design configuration. Keep authorization and request handling in the server application contract.

A diagram can be an uploaded SVG asset referenced by a mapped image field. It does not need to be pasted into a description as layout markup.

A section may have authored fallback data. Once a mapping supplies that field, edit the mapped source. Editing the fallback may produce no visible change.

How this scales in practice

A reusable template can render many records and sites. A shared correction then fixes the renderer without requiring edits to every article. A content correction stays in its owning module. Agents can make narrow changes because the boundaries are explicit.

This does not prove unlimited scale. Generation time, snapshot size, database queries, media delivery and concurrent editing still need measurement. A clean mapping also does not prove that a checkout or password-reset action works. Use it as a structural check, then test the behavior.

Inspect before changing

Read the board, agent context and page flow. Follow the path from the requested URL to its HMVC action, page, section, template and source. Record which field you intend to change.

Continue with the JSON structure and data mapping.

Implementation references

Repository references: app/library/DataboardPatchDelta.php; app/backend/login/models/WebsiteDeployedHmvcTrait.php; app/antsand_bootstrap/project/common_views/common/common_init_modern.volt.