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.
Content workflow
Docs and Changelog together
Maintain reference material and release context in the same Framer project as part of one development workflow.
Documentation and release notes often drift apart because they are written in different tools at different times. MokuDocs 2.0 keeps both in the same Framer project.
Different jobs, shared workflow
Docs explain how something works. Changelog records what changed and when. They are separate CMS collections because the content has different shapes, but they share a design system, publishing flow, and home.
Work alongside development
When a feature is ready, ask two simple questions:
Does an existing Doc need to change, or does a new Doc need to exist?
Is the change meaningful enough to record in Changelog?
Answering them together prevents the usual gap between shipping a feature and explaining it.
Keep release notes concise
A Changelog entry should name the change, explain why it matters, and link readers toward the relevant Doc when more detail is needed.
One place to maintain
The goal is not more process. It is less context switching: develop the product, update the Docs, record the release, verify the site, publish.