A Fifth Editor Block: Update, for Hand-Written Changelogs

The last two posts covered Mermaid and Accordion, then Columns and Frame — content types and layout. This one is narrower: a single block for the specific job of writing a changelog or release-notes page by hand, inside a normal MDX doc.

What it does#

Update turns one entry into a heading with its own anchor, so a reader (or a link from a release email) can jump straight to "what changed on Oct 14" without scrolling past everything above it:

That's three stacked <Update> blocks, written directly in this post. Hover any of the headings above and a # link appears — each one is independently shareable. The syntax:

<Update label="v0.4.0" description="2026-10-14">
  Added dark mode to the component reference.
</Update>

label is required — it's the heading text and the slug the anchor is built from, so keep labels unique on a page. description is optional, usually a date or version number underneath the label. The body is ordinary MDX: prose, a code block, a list, whatever the entry needs.

This is not the same thing as Dokly's changelog feature#

Dokly also has a real, database-backed changelog: a dashboard editor, a public page at <project>.dokly.co/changelog, and (for connected agents) an add_changelog_entry MCP tool that drafts entries from the terminal. That system is for a changelog as a product feature — structured entries, a feed, a page Dokly renders for you.

Update is the opposite: it's a plain MDX component for when you want a changelog, release notes, or a "what's new" section as a page you write yourself — inside a doc, versioned alongside your content, with full control over what surrounds it. Use the dashboard changelog if you want Dokly to manage the page. Use Update if you're already writing a page in the editor and want a clean way to list dated entries inside it.

What this doesn't do#

Mintlify's version of this component also takes tags (an array, for filtering entries by category) and rss (for generating a feed). Both are left out here, deliberately: they're array and object props, and nothing in Dokly's MDX round-trip — the part that keeps your content intact when you open it back up in the editor — handles array or object attributes yet. Every prop on every component we ship today is a string, a boolean, or a number. Adding tags or rss means adding that support first, and neither has anything to consume it on Dokly's side yet (no tag-filter UI, no feed generator). If that changes, this is the component it comes back to.

That brings Dokly to 17 top-level MDX components, up from 11 a few weeks ago. Still-missing: Panel, Expandables, Tooltips, Tree, and Fields. Those are the next batches.

If you write release notes by hand and this doesn't cover how you do it, reply to this post or use the contact page — it reaches me directly.

Changelog entries#

Update component · Added · A block for hand-written changelog and release-notes entries in MDX — each label becomes its own linkable heading, with an optional date or version line underneath.