Product updates let you announce new features, improvements, and fixes to your users. They appear on the Updates page and can be shown as popup notifications in the beacon widget.
Creating an update
Create a markdown file in content/updates/ with the date in the filename:
content/updates/2026-02-13-my-new-feature.md
Add frontmatter:
---
title: "My New Feature"
slug: "my-new-feature"
date: "2026-02-13"
category: "new"
showModal: true
---
Describe what changed and why it matters.
Frontmatter fields
| Field | Required | Description |
|---|---|---|
title | Yes | The update title |
slug | Yes | URL-safe identifier for the update |
date | Yes | Publication date in YYYY-MM-DD format |
category | Yes | One of: new, improvement, fix, announcement, coming-soon |
showModal | No | Set to true to show as a popup in the beacon widget |
Category badges
Each category renders as a colored badge on the update:
- new — A brand new feature
- improvement — An enhancement to an existing feature
- fix — A bug fix
- announcement — General news or information
- coming-soon — A preview of upcoming features
Beacon modal notifications
When showModal is set to true, the update will appear as a popup notification in the beacon widget for users who haven't dismissed it yet.
- Users can dismiss the modal, and the dismissal is saved in localStorage.
- Updates older than 6 months are never shown as modals, regardless of the
showModalsetting. - If a user is identified via
Markdesk.identify(), dismissals are tracked per user ID.
Adding images
Place images in public/images/updates/ and reference them in the markdown body:
Don't duplicate the first image — if it appears in the content body, that's sufficient.