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.
Index
Documentation for MokuDocs 2.0, from setup to delivery.
All
MokuDocs 2.0
Start here
Content workflow
Reference
Release & quality
Title
Category
Updated
MokuDocs 2.0
A lean, CMS-native documentation template for Framer that keeps authoring and reading simple.
MokuDocs 2.0
Create your first Doc
Add a CMS item once and let MokuDocs create the page, navigation, and home listing.
Start here
Categories
Use a small set of CMS categories to keep the sidebar understandable and easy to maintain.
Content workflow
Table of contents
Headings in rich text create a quiet reading rail that helps readers navigate long documentation.
MokuDocs 2.0
Bookmarks
Let readers pin useful Docs in their own browser without accounts or authoring overhead.
MokuDocs 2.0
Glossary
Maintain recurring terminology in a native CMS collection and let readers get definitions without leaving the page.
Content workflow
Brand and visual system
Change the essentials in Framer’s native panels while preserving a calm, consistent documentation experience.
MokuDocs 2.0
From MokuDocs 1.0 to 2.0
Why 2.0 keeps the useful reading features while reducing authoring and customization complexity.
Start here
Duplicate the template
Start with a Framer duplicate, then make the minimum changes needed to make MokuDocs your own.
Start here
The minimal setup loop
A practical first session: brand the template, write one Doc, record one change, and verify the result.
Start here
Set up your Framer project
Understand the CMS collections and native editing surfaces before you add your team’s documentation.
Start here
Design your documentation structure
Build an information architecture that follows reader needs and stays manageable as the product grows.
Content workflow
Write structured content
Use Framer rich text and meaningful headings to produce pages that are readable, searchable, and easy to maintain.
Content workflow
Docs and Changelog together
Maintain reference material and release context in the same Framer project as part of one development workflow.
Content workflow
The development documentation loop
A lightweight release habit for keeping product work, Docs, and Changelog aligned.
Release & quality
Keep operations lightweight
MokuDocs 2.0 avoids introducing accounts, billing logic, or configuration layers that do not help documentation.
MokuDocs 2.0
Native Framer editing
Use Framer CMS, canvas, and shared styles in the roles they are designed for.
MokuDocs 2.0
Accessibility and semantic structure
Preserve the reading and interaction foundations that make MokuDocs 2.0 usable across devices and input methods.
Release & quality
Content portability
Keep documentation content in clear CMS fields so it remains easy to review, revise, and carry forward.
Release & quality
Reading and keyboard navigation
How the documentation interface supports focused reading, direct navigation, and keyboard access.
Reference
Troubleshoot your docs
Practical checks for the common CMS, publishing, and responsive-reading issues in a Framer documentation project.
Reference
FAQ
Answers to common questions about operating MokuDocs 2.0 as a Framer-native documentation system.
Reference
CMS reference
A concise reference for the MokuDocs 2.0 collections and the information each one owns.
Reference