Makerkit 2.20 includes support for a SaaS changelog functionality, allowing you to share your updates with your users. We've had a changelog on this website for a while now, and it's now available in your Makerkit-powered SaaS too.
Why should you write a changelog for your SaaS? The Linear blog post explains it well, but in short: it builds trust with your users, and helps you communicate your progress and roadmap to your users. Give it a read.
How to add changelogs to your SaaS
In Makerkit, the changelog page can be accessed at /changelog - each entry has its own page (important for SEO purposes) at /changelog/[slug].
To add a changelog entry, you can create a new Markdoc file in the content/changelog folder. The file name should be the slug of the changelog entry.
Changelogs entries have the same format Cms.ContentItem like blog posts and documentation pages.
Here is an example:
---title: "Security enhancements and SSO"description: "Major security updates including SAML SSO, audit logs, and enhanced access controls to keep your data safe and compliant."categories: []tags: []image: ""publishedAt: 2025-08-20status: "published"---Start writing your changelog today
Whether you're just starting out or have an existing SaaS and are updating to Makerkit 2.20, make sure to take some time and add all the changelog entries to your SaaS. This will help communciate your visitors about the progress of your SaaS, your journey, and your roadmap.
If you have any questions or feedback, please don't hesitate to contact us.