CMS
Framer’s built-in content system. In MokuDocs 2.0, it is the primary place where authors create and maintain documentation.
Doc
One item in the Docs collection. A Doc provides a title, description, category, rich-text content, and optional update date.
Category
A CMS item that groups Docs in the sidebar and keeps the information architecture visible without manually building navigation.
Changelog
A chronological record of meaningful changes. It is managed beside Docs in the same Framer project, with its own CMS collection and page.
Rich text
The native Framer CMS field used for a document body. It supports headings, lists, tables, images, links, quotes, and code blocks.
Native
A feature managed through Framer’s canvas or CMS rather than a custom configuration layer. MokuDocs 2.0 favours native controls wherever possible.
Breakpoint
A layout range in Framer. MokuDocs 2.0 uses desktop, tablet, and phone breakpoints to adapt reading and navigation.
Mobile drawer
The full-width phone navigation surface used for Docs, page switching, and changelog tags without crowding the reading area.
Color Style
A reusable Framer color token. Updating a Color Style changes the related interface color consistently across the project.
Text Style
A reusable Framer typography rule. It keeps headings, body copy, navigation, and metadata consistent without per-page formatting.
Table of contents
A reading rail generated from H2 and H3 headings in a Doc’s rich-text content. It helps readers move through longer articles.
Bookmark
A reader-side pin stored in the browser. It marks useful Docs without adding accounts, permissions, or CMS complexity.
Saved highlight
A reader-side text selection saved for later, similar to a bookmark but scoped to a specific passage. Saved highlights are stored in the browser and can be reopened, edited, or removed from the header panel.
Tag
A short label used to group and filter Changelog entries. Tags are managed in their own CMS collection and referenced from each Changelog item.
MokuDocs 2.0
Table of contents
Headings in rich text create a quiet reading rail that helps readers navigate long documentation.
MokuDocs 2.0 generates the table of contents from headings in a Doc’s rich-text content.
Use headings as structure
Use H2 for major sections and H3 for supporting detail. Paragraphs, lists, images, and quotes do not create table-of-contents entries.
What readers see
On desktop, the page shows a compact rail beside the article. It tracks the current section and expands into the full heading list when readers interact with it. On phone layouts, the rail is intentionally removed so the reading column stays uncluttered.
No separate outline
There is no second outline to edit or sync. Change a heading in the CMS body and the document structure changes with it.
Write with intent
A page with clear H2 sections is easier to scan, easier to revisit, and easier for assistive technology to understand. The table of contents is a result of good writing structure, not extra administration.