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.
Start here
The minimal setup loop
A practical first session: brand the template, write one Doc, record one change, and verify the result.
The fastest way to understand MokuDocs 2.0 is to complete one small publishing loop.
1. Brand the shell
Replace the logo, product name, and accent color. These changes establish ownership without disturbing the underlying system.
2. Create one useful Doc
Add a real page in the Docs collection. Use a title, short description, category, and a body with H2 headings.
3. Add the related Changelog entry
If the page documents a shipped change, create a Changelog item in the same Framer project. Keep it short: what changed, why it matters, and where readers can learn more.
4. Review at desktop and phone sizes
Check that the sidebar, reading column, table of contents, and mobile drawers serve the content rather than competing with it.
5. Publish
Publish when the content and change record agree. This loop is the operating model: build, document, record, review, publish.