Radiant Docs helps teams keep documentation useful without forcing every change through the same workflow. Writers can edit in the dashboard, developers can work from source files, and the writing agent can help revise docs from plain language instructions.
All of those workflows update the same docs source. Radiant then builds, publishes, and indexes the docs so readers can browse pages, search content, and ask questions in natural language.
The product model
Radiant is built around one source of truth and several ways to change it.
| Layer | What it does | Why it matters |
|---|---|---|
| Docs source | Stores docs.json, MDX pages, images, videos, and OpenAPI files | Keeps content portable and reviewable |
| Authoring tools | Let people edit visually, with the agent, or from source files | Lets each contributor use the workflow that fits the change |
| Publishing | Builds the docs site and deploys updates | Turns reviewed changes into a live reader experience |
| Assistant context | Indexes published docs and approved context sources | Lets readers ask natural-language questions and get cited answers |
One source, several editors
Radiant supports multiple authoring styles because docs work rarely belongs to one kind of teammate.
- Use the dashboard for small edits, page organization, settings, and no-code publishing.
- Use the writing agent when you want help drafting, rewriting, restructuring, or cleaning up docs.
- Use Markdown and
docs.jsonwhen you want direct source control, local preview, and Git-based review.
These are not separate docs systems. They are different ways to update the same documentation source.
Draft, publish, deploy
Dashboard and agent-assisted changes are made in a draft. Saving keeps the draft up to date. Publishing moves the draft into the live docs source and starts a deployment.
For GitHub-backed projects, source-file changes can also start deployments when they are pushed to the connected branch. Radiant watches for relevant docs changes, builds the site, and shows deployment progress from the dashboard Overview page.
Docs as an answer surface
Radiant docs are meant to be read by people and used as context for answers. Clear headings, step titles, tables, links, and OpenAPI descriptions help readers scan pages and help Ask AI retrieve the right source material.
That is why the best Radiant docs include both:
- Practical steps for completing tasks.
- Conceptual context that explains when, why, and how a feature should be used.
When a user asks the assistant a question, Radiant retrieves relevant approved context, generates an answer, and links back to the source pages it used.