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.
Reference
FAQ
Answers to common questions about operating MokuDocs 2.0 as a Framer-native documentation system.
Is MokuDocs 2.0 a product application?
No. It is a Framer documentation template. The sample content explains the template and should be replaced with your own product documentation.
Do I need to edit the canvas for every new article?
No. Create and maintain ordinary articles in the Docs CMS collection.
Can I manage Docs and Changelog together?
Yes. They are separate CMS collections in the same Framer project, with one design system and publishing workflow.
What did 2.0 keep from 1.0?
CMS-driven navigation, a table of contents, and bookmarks remain because they make documentation easier to read and maintain.
Can I change the visual design?
Yes. Start with the logo, product name, Color Styles, and Text Styles. Keep shared changes in shared styles.
Does mobile use the same navigation?
It uses the same CMS content but presents navigation through full-width drawers so the article remains easy to read.