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
From MokuDocs 1.0 to 2.0
Why 2.0 keeps the useful reading features while reducing authoring and customization complexity.
MokuDocs 2.0 is a redesign, not a cosmetic upgrade.
What was worth keeping
Three ideas from 1.0 remain because they continue to help readers and authors:
CMS-driven sidebar navigation
A table of contents for longer Docs
Browser-based bookmarks
What changed
2.0 reduces the number of collections, fields, components, and editing paths that a buyer needs to understand. The intent is not to remove capability for its own sake. It is to remove routine decisions that do not improve the documentation.
Native-first by default
Where Framer provides a suitable native CMS or canvas feature, 2.0 uses it. This makes the project easier to inspect, customize, and hand off.
The result
Authors spend less time managing layout. Readers get a simpler, more consistent surface. The template becomes a practical place to maintain Docs and Changelog alongside product development.