Readable operating docs, not hidden product state.
Matic keeps its operating model in plain files. The docs surface should explain how orgs, projects, previews, channels, and framework rollouts fit together without inventing a second control plane.
Repo-backed content with typed sections.
This page now renders from JSON files in the repository instead of route-local placeholder copy.
The first docs pass should cover the system boundary clearly.
These are the topics worth making editable in content first, before layering richer docs navigation on top.
- How org structure maps to files, directories, and reusable framework material.
- How project repos, worktrees, previews, and delivery status hang together.
- How channels, provider adapters, and plugins extend the operating model.
Start with durable concepts, then expand into task-level workflows.
The docs page can evolve into a proper documentation hub, but the content model should start with a small number of reliable section types and strong editorial structure.
In the near term, this page is a repo-backed managed page. Editors can update headings, summaries, and section copy without touching route code.
Once the page model is stable, the same system can support richer documentation index pages, linked guides, and comparison or changelog content.
Use the admin to evolve this page before you lock a heavier CMS flow.
The point of this first implementation is to make page structure and translations editable in git while keeping the rendering layer typed and inspectable.