Authoring Docs
The rendered documentation source is the content/ directory. Every .md and .mdx file inside that tree is discovered by the content loader.
File paths become routes
| File | Route | Slug |
|---|---|---|
content/getting-started.md | /docs/getting-started | getting-started |
content/authoring/index.mdx | /docs/authoring | authoring |
content/authoring/frontmatter.md | /docs/authoring/frontmatter | authoring/frontmatter |
content/rendering/components.mdx | /docs/rendering/components | rendering/components |
Use folder index.md or index.mdx files when a section should have its own landing page.
Markdown and MDX
Use .md for straightforward prose and .mdx when you want React components in the page body. Both extensions go through the same loader, validation, ACL checks, and navigation builder.
content/
getting-started.md
authoring/
index.mdx
frontmatter.md
navigation.md
rendering/
index.mdx
components.mdxSection pages
A section page is just an index file in a folder. It can contain normal content, or it can render a grid of its direct child pages:
Frontmatter Reference
Every supported frontmatter field, what it controls, and how the application uses it.
ViewNavigation Model
How content files, frontmatter, access rules, and scoped sidebars become the rendered menu.
ViewMkDocs Headers and Headings
How MkDocs-style page headers, Markdown headings, anchors, and table-of-contents behavior map to Nexus Docs.
ViewAuthoring rules
- Keep one topic per page.
- Use
summaryas the search and SEO description. - Use
nav_orderfor predictable menu order. - Use
nav_hidden: truefor pages that should be reachable by URL but absent from menus. - Use
status: draftwhile writing. Drafts are hidden unless the viewer is an admin. - Use
status: deprecatedwhen a page should remain visible with a warning banner.
If you want to demonstrate a component, prefer rendering the real component in the docs and then showing the source snippet below it.