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
Keep operations lightweight
MokuDocs 2.0 avoids introducing accounts, billing logic, or configuration layers that do not help documentation.
MokuDocs 2.0 is a documentation template, not an application platform.
Deliberate boundaries
The template does not add user accounts, permissions, billing controls, workflow automation, or product APIs. Those concepts can be useful in a product, but they should not be invented inside documentation just to make a demo feel more complex.
Fewer moving parts
The project focuses on content, navigation, search, glossary, bookmarks, responsive reading, and release notes. Those are the parts that directly support a documentation experience.
Benefits for buyers
A smaller operating surface is easier to duplicate, understand, brand, and maintain. It also makes it clearer which changes belong in CMS and which belong in the shared design system.
Extend only when needed
If your product needs additional integrations or data, add them intentionally after the documentation basics are working. Start with the lean system; do not inherit complexity by default.