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
Troubleshoot your docs
Practical checks for the common CMS, publishing, and responsive-reading issues in a Framer documentation project.
When something looks wrong, check the smallest relevant layer first.
A Doc is missing from navigation
Confirm that the Docs item has a Category and is not left as a draft. Then check the Category order and the Doc order in CMS.
The table of contents is empty
Add H2 or H3 headings in the Content field. Ordinary paragraphs and bold text do not create entries.
A change is not visible on the public site
Confirm the CMS item is saved, then publish the Framer project. Allow a short time for the public build to refresh before diagnosing a layout issue.
Mobile navigation feels wrong
Check the Phone breakpoint and test the drawer controls at a narrow width. Avoid forcing desktop-sized controls into the phone header.
A visual change is inconsistent
Look for a local override first. If the change should apply everywhere, update the shared Color Style or Text Style instead.