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.
MokuDocs 2.0
MokuDocs 2.0
A lean, CMS-native documentation template for Framer that keeps authoring and reading simple.
MokuDocs 2.0 is a documentation template for Framer. It is designed for teams that want a calm, readable documentation site without turning documentation into a second product to maintain.
Tip: select any text on any page to create a Saved highlight. Add a note, then find it again later from the highlights icon in the header.
The idea
The daily workflow is intentionally short:
Duplicate the template.
Replace the brand basics.
Add or update content in Framer CMS
Record meaningful changes in Changelog
Publish when the work is ready.
A Doc is a CMS item, not a custom page to assemble. The site structure follows that content automatically.
What 2.0 keeps
MokuDocs 2.0 keeps the features that reduce reading and maintenance friction: CMS-driven navigation, a table of contents for long pages, bookmarks, search, and responsive navigation.
What's new in 2.0
A Glossary, Saved highlight, and Changelog are new to 2.0. Glossary turns a term into a definition readers can open without leaving the page. Saved highlight lets a reader select any passage, save it with a note, and find it again later from the highlights icon in the header. Changelog gives every release its own entry, filterable by tag. None of the three existed in 1.0.
What 2.0 removes
It removes the extra setup layers that made 1.0 heavier to operate: complex content structures, parallel editing paths, and routine canvas work for ordinary documentation updates.
One place for Docs and Changelog
Docs and Changelog are separate CMS collections, but they live in the same Framer project, share the same visual system, and publish through the same workflow. A product team can document a feature while building it, then describe the release in Changelog without switching tools or duplicating information.