Development and maintenance
For contributors working on this checkout. Read Build and test before running commands, then Local development for a full authenticated CMS/frontend. Use the source map to choose a package and the editor guide for browser state/security. Documentation conventions apply to every docs change. No deployment, push or external-service modification is implied by these local procedures. Return to the contributor guide. Customer terminology is in glossary.
Files and folders in this directory
| File or folder | Detailed scope |
|---|---|
| README.md | Contributor reading order and index of every direct development file. |
| build-test.md | Go/Node prerequisites, workspace-aware checks, editor/browser/database tests, container builds, CI reality and doc verification. |
| local-development.md | Isolated temporary storage/auth files, loopback PKCE sign-in, separate CMS/frontend ports, Vite limits and shutdown. |
| repository.md | Top-level source map, component packages, dependency purposes, generated/optional files and where interface changes belong. |
| examples.md | Build scripts, C/Go/Rust compilers, standalone theme packages, integration verification and GitLab generic-registry publishing. |
| editor.md | Tiptap/GrapesJS source boundary, browser module map, same-origin API, expiry checkpoints, CSP/preview isolation and bundle behaviour. |
| documentation.md | Canonical homes, detailed direct-child README rules, complete procedure conventions, link relocation and local validation. |