Changelog

Each tag in the changelog filter now shows a count, so the panel reads Design (3) rather than Design. You can see where the changes have been concentrated before you filter anything. The count is the total for the whole changelog, not for whatever filter is currently applied, so it does not move as you tick boxes.

The numbers are worked out from your own entries. Nothing needs to be typed in or kept up to date, and no field was added to the Changelog or Tag collections. A tag that no entry uses shows (0), which you can switch off in the component's properties.

One thing to expect while editing: on the canvas Framer draws a single preview row rather than the whole collection, so the counts there will read (1) and (0). Open a preview or publish to see the real totals.

On a phone, the category tag in the home list now sits beside the date on the second line of every row. Short category names could previously end up on the first line instead, pushed to the far right, because the row was holding space for an element that is not part of the layout. Only short names fell into that gap, which is why it looked random rather than consistent.

The previous and next links at the foot of a doc now shorten with an ellipsis when a title is too long for the space. They previously ran into one another with nothing between them, and on a phone the end of the next title, along with its arrow, could sit beyond the edge of the screen. Both links now keep a fixed gap between them and the arrows stay in place. Short titles are unchanged.

If you duplicated the template before this date, message us through the Marketplace and we will send the two updated files.

The menu that opens from the changelog page now carries a heading of its own, the way the docs menu does, so it is clear which menu you are looking at before you read the rest of it.

The theme row at the foot of every mobile menu now sits at the same height with the same spacing, whichever menu you open.

The words beside the light and dark toggle are now part of the button, and the button spans the full width of the row, so anywhere in that row responds to a tap. Until now the words were a separate label: tapping the icon worked, but tapping the words did nothing on the changelog menu, and on the docs menu it dismissed the menu and returned the reader to the page behind it, which looked like the button had jumped somewhere.

The label now names the action it will perform, Switch to light theme or Switch to dark theme, and reads the same to a screen reader as it does on screen. The theme row also sits at the same height in every menu.

The navigation drawer now marks the doc you are currently reading, the way the desktop sidebar already did. Every row used the same muted colour before this, so a reader opening the menu had no indication of where they were in the documentation.

Tapping an item in the mobile navigation drawer now opens that page with the menu closed. Previously the open state of the drawer travelled in the page address, so the next page arrived with the same full screen menu still covering it. The tap had worked every time, but nothing appeared to happen, and a second tap was what eventually got the reader out.

Menu links now drop that state before navigating, so a page opens ready to read.

A reader who chooses light or dark now keeps that choice on a phone. Previously the setting was restored only where the theme control itself was on the page, and the phone header does not carry one, so every mobile page view fell back to the default and a choice made inside the navigation drawer was lost on the next page.

The theme is now established by the skip-to-content control, which is present on every page at every screen size. If you change the default theme, set it in both that control and the theme toggle so the two agree.

The light and dark toggle inside the mobile navigation drawer now works without dismissing the drawer. Tapping it previously flipped the theme and closed the drawer in the same gesture, and the tap could carry through to whatever the drawer had been covering. The toggle now handles its own tap directly, the same way the pin control beside it already did.

Note that the words next to the toggle are a label rather than a second button, so tap the icon itself. A combined control is planned.

The Glossary and Saved highlights buttons in the header now work as toggles: tap to open, tap again to close. Previously they only opened their panel, and on phones the open panel covered the menu button, which could make navigation appear broken. Both buttons also have larger tap areas on touch screens, with no visual change. If you duplicated the template before this date, message us through the Marketplace and we will send the two updated files.

Readers can now select any passage in a Doc and save it as a highlight. Saved highlights persist in the browser, open from a header panel alongside Glossary, and can be reopened, edited, or removed without leaving the article.

Changelog entries can now be filtered by Tag. On phone, the mobile drawer includes a dedicated Tags panel so readers can narrow the list to the kind of change they care about, such as Design, Content, or Release.

Phone navigation now uses simple full-width drawers for Docs, page switching, and changelog tags. The reading surface stays clear while the same CMS structure remains available on every breakpoint.

Semantic landmarks, keyboard support, skip navigation, contrast improvements, accessible labels, and responsive interaction patterns were consolidated into the template baseline.

The template keeps the 1.0 features that improve reading and maintenance: CMS-driven navigation, a table of contents, and bookmarks. Redundant setup and visual complexity were removed.

Docs, Categories, Glossary, and Changelog are managed in one Framer project. Adding a Doc through CMS creates its page, sidebar entry, home listing, and reading structure without a canvas step.

MokuDocs 2.0 added a native Glossary CMS collection. Readers can open definitions from a header panel or click a linked term inline without leaving the article they are reading, and authors maintain terms the same way they maintain Docs.

MokuDocs 2.0 establishes a new Framer-native documentation system. The information architecture, CMS model, visual language, and authoring workflow were rebuilt rather than carried forward from 1.0.

MokuDocs 1.0 launched on the Framer Marketplace as a CMS-powered documentation template with category-based sidebar navigation, Cmd+K search, light and dark mode, a bookmark system with continue-reading, an auto-generated table of contents, reading progress, and 18+ sample docs. It shipped as a free listing to establish ranking ahead of a later price change.