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
Duplicate the template
Start with a Framer duplicate, then make the minimum changes needed to make MokuDocs your own.
Begin by duplicating MokuDocs 2.0 into your Framer workspace.
First pass
Before editing individual articles:
Replace the logo and product name.
Review the Accent Color and Text Styles.
Open the CMS collections.
Decide which sample content to keep, rewrite, or remove.
Do not rebuild the canvas
The template is already connected to CMS. For normal content work, opening the canvas adds steps without improving the result.
Make it recognisable
Replace the visible sample copy before publishing. Update metadata, social links, and any placeholder images so the site clearly represents your product.
Keep a clean starting point
Use the duplicate as your documentation workspace. It keeps Docs, Changelog, design styles, and responsive layouts together rather than scattering them across separate tools.