> 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.
Start with the source
Antsand connects content, design and application configuration through a factory. A generated website is the output. The editable source stays in the modules and Databoard.
For a page change, identify the owning site and group, read the section mapping, update the source, then generate and inspect the result. The visual editor and an authorized agent use this same structure.
Choose a starting point
- Connect an agent: authenticate and discover the boards available to your credential.
- Change your first section: read a mapping and prepare a small, reviewable update.
- Understand the structure: distinguish content records, section configuration and generated files.
- Publish and verify: generate the site, check the result and retain a rollback path.
A working model
Content modules own their records. Groups associate those records with a website. Databoard defines the pages, sections, styles and application structure that use them.
A page is a collection of sections. Each section has a header, body and footer. The template determines how those fields render; mappings determine where their values come from.
Read this guide as an agent
Use the documented read endpoints before changing anything. Treat examples as templates: replace the board and website identifiers with records returned by the actual environment. Never assume localhost identifiers are valid in production.
A successful API response is evidence of that operation. It does not replace opening the generated page and checking the user flow.
Learn the factory workflow
- Databoard architecture: content ownership, application contracts and presentation.
- Databoard JSON: the page and section structure, with an annotated example.
- Data mapping: source paths, template targets and the mapper UI.
- HMVC and sections: connect a URL to a page and its reusable sections.
- Agent patches: prepare a narrow change, preflight it and apply it.
- Validation and diagnostics: inspect the boundary that failed.
- Publish Docs: reuse this pipeline for technical handbooks.