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
Content portability
Keep documentation content in clear CMS fields so it remains easy to review, revise, and carry forward.
MokuDocs 2.0 keeps content in native CMS fields rather than embedding it inside one-off canvas pages.
Clear ownership
Docs contain titles, descriptions, categories, rich-text bodies, and update dates. Changelog entries contain version context, titles, dates, and content. Glossary terms remain independent from article pages.
Easier review
Because the information is structured, a team can review the content model directly in CMS rather than searching through many page layers.
Easier revision
A change to a product workflow usually changes a small number of Docs and possibly one Changelog entry. The CMS model makes those updates explicit.
Plan your own exports
Your Framer workspace and publishing plan determine how you retain or export project information. Keep your source writing and product decisions in the places your team already trusts; MokuDocs is the presentation and maintenance layer for reader-facing documentation.