Integration and implementation reference
Use these documents when writing integrations, debugging exact behaviour or changing a shared interface. Start with Contracts, then API and Configuration. These pages are intentionally more technical than the site owner guides. For runnable install/recovery procedures use operations. The glossary defines acronyms; documentation home links customer guides. Return to the contributor guide for development.
Files and folders in this directory
| File or folder | Detailed scope |
|---|---|
| README.md | Scope, reading order and index of every direct reference file. |
| contracts.md | Cross-component Website spec/status, auth keys, generated naming, images, ports, paths and compatibility contracts. |
| api.md | CMS routes, authentication/error semantics, request/response shapes, page/settings/assets operations and publication results. |
| configuration.md | Runtime entry points, volume preparation and build/HTTP identity; links to canonical flag tables. |
| storage.md | Durable mutations, close handling, recovery journals and snapshot lifetimes; links to volume layouts. |
| frontend.md | Local execution, implementation boundaries, release resolution, benchmarks and source layout. |
| content.md | Versioned page envelope and format rules, Markdown/visual editing/rendering, Index semantics and theme boundaries. |
| navigation.md | Menu API metadata, parent identity, directive handling and generated navigation hooks. |
| themes.md | Native component/binding templates, workspace semantics, ZIP manifest/assets/limits, storage/API and Forge placeholder. |
| wordpress.md | WordPress inspection/apply API and browser/database verification tools. |
| extensions.md | Raw object fields, repeater attributes/bindings, plugin operations, ZIP schemas, block packages and WASI renderer ABI/examples. |