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.
Release & quality
The development documentation loop
A lightweight release habit for keeping product work, Docs, and Changelog aligned.
MokuDocs 2.0 treats documentation as part of delivery, not a task left for later.
During development
Capture decisions that change how users understand, configure, or use the product. A short note is enough until the implementation settles.
Before release
Update the relevant Doc or create a new one. Review its category, headings, description, and related links.
Record the change
Create a Changelog entry when the release is meaningful to readers. Keep it factual and short. The detailed explanation belongs in Docs; the context and timing belong in Changelog.
Verify the surface
Check desktop and phone layouts, links, search, and reading order. Then publish the project once the documentation and release note describe the same reality.
Repeat
The benefit comes from repetition. A small reliable loop is more useful than a large documentation process that only happens occasionally.