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
Brand and visual system
Change the essentials in Framer’s native panels while preserving a calm, consistent documentation experience.
MokuDocs 2.0 is designed so that the usual brand changes stay in Framer’s native editing surfaces.
Change the essentials
Most teams only need to update:
Logo
Product name
Accent color
Fonts
CMS content
Use styles, not one-off fixes
Color Styles and Text Styles keep the interface consistent. Change a shared style when you want a system-wide adjustment instead of restyling individual pages.
Keep the reading surface quiet
The template intentionally uses a restrained visual system. Avoid adding cards, borders, badges, or controls simply because they are available. The strongest documentation interface makes the content easier to scan and the next action obvious.
Separate brand from structure
Your brand can change without changing the CMS model, page hierarchy, or authoring workflow. This separation is what keeps the template easy to adapt after duplication.