Separate update pages get ignored
A public changelog is important, but many users only notice updates inside the product.
Changelog widget
Put product updates where users already are.
ChangeCrab widgets bring your latest release notes into your app, docs, marketing site, or dashboard while keeping the public changelog as the source of truth.
One hosted changelog can power widgets, RSS, badges, and subscriber emails.
Sidebar
Inline
Badge
5 min
Typical embed setup for a simple widget
1
Script can point to the same public changelog
3
Widget, RSS, and email all reinforce each update
Widget preview
Slideout changelog
A compact launcher opens recent updates without sending users away from your app.
Embedded update feed
Show release notes in docs, account pages, onboarding flows, or customer portals.
Activity indicator
Signal that your product is actively maintained from your README, site footer, or pricing page.
New update ready for customers
Published to public page, widget, RSS, and subscriber channels.
Follow-up context stays attached
Links, categories, and customer impact live with the update instead of drifting across tools.
The problem
Most users will not go looking for your changelog.
Banners disappear too quickly
One-off announcements vanish. A widget keeps recent updates accessible.
Unread signals help users notice updates
A small indicator can bring users back to improvements they would otherwise miss.
Workflow
Widget-first product update distribution
Source
Publish the changelog entry
Create a clear release note in ChangeCrab.
Shape
Embed the widget once
Add the script where users naturally check for product changes.
Publish
Keep every channel synced
New posts appear in the widget and remain available on the public changelog.
Implementation
Embed examples for changelog widgets
Add the widget once, then keep publishing through ChangeCrab while the embedded surface stays up to date.
<button class="changebubble">Product updates</button>
<script>
window.changecrab_config = {
projectid: "your-project-id",
type: "sidebar",
selector: ".changebubble",
activecolor: "#16a34a"
};
</script>
<script src="https://changecrab.com/embed/embed.js"></script><div id="product-updates"></div>
<script>
window.changecrab_config = {
projectid: "your-project-id",
type: "inline",
selector: "#product-updates"
};
</script>
<script src="https://changecrab.com/embed/embed.js"></script>[](https://changecrab.com/changelog/your-slug)What you get
Built around the parts of product communication teams use every week.
Sidebar and inline update experiences
Unread indicators and activity badges
Public hosted changelog as the source of truth
Brandable pages and custom-domain support
Subscriber capture for users who want email updates
RSS and API options for technical audiences
Widget details
The widget should make updates discoverable without hijacking the product.
Buyers need to see that the widget is a surface for the changelog, not an interruptive announcement layer.
Header, help menu, settings area, docs, dashboard, and footer placements are easier to find repeatedly.
Recent updates should be scannable, with full context on the permanent changelog entry.
The widget, public page, RSS feed, and subscriber email should all reference the same approved update.
Buyer questions
Questions teams ask before choosing a changelog workflow.
Do I need to rebuild my changelog UI?
No. Use ChangeCrab as the hosted source and embed the widget where you want updates to appear.
Can the widget match my brand?
Yes. ChangeCrab is designed for branded changelog experiences, including custom domains and visual controls.
Should I still have a public changelog page?
Yes. The widget is for visibility inside your product; the public page is the permanent, shareable archive.
Make every product update easier to discover.
Create a ChangeCrab changelog and add a widget where your users already work.