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.
Content workflow
Glossary
Maintain recurring terminology in a native CMS collection and let readers get definitions without leaving the page.
The Glossary collection holds short definitions for terms that recur across the documentation.
Use it for repeated language
Good glossary terms are product names, abbreviations, CMS concepts, or workflow words that appear in more than one document. A concept explained once in a single article usually belongs in that article instead.
Add a term
Open the Glossary collection in Framer CMS.
Create a new item.
Set Term to the exact word or phrase readers will see linked in Docs and Changelog content.
Write Definition in the rich-text editor. Links, lists, and emphasis are supported, the same as in a Doc.
Publish the project.
Link a term in content
Open the Doc or Changelog item you want to link from.
Select the word or phrase that should trigger the definition.
Apply a link to the selection and leave the link's URL empty, for example
<a>CMS</a>in the HTML view.Check that the linked text matches an existing Glossary item's Term field exactly, including capitalization.
Publish and confirm the link opens the definition in the side panel instead of navigating away.
Linking text that has no matching Term still renders, but as a plain, non-interactive link.
Reader experience
The glossary panel can be opened from the header. Linked glossary terms can also open a definition without taking readers away from the article they are reading.
Keep definitions compact
A glossary is an aid to reading, not a second documentation tree. Define the term, explain why it matters, then link to a full Doc when deeper guidance is needed.