Tell users what you shipped, right inside your product.
The widget is a view of work you already track, so there is nothing to write twice. Place one container and your releases appear.
14 day trial. Card up front, charged after it ends.
Your latest release is the first thing people see.
Each release shows its name, what shipped and the date. Five load at a time, with a show more button.
People who only want the news read the top. People who want the history keep going.
Show people their request made it.
Each shipped feature shows how many people asked for it. Items can carry a type: new, improvement, fix, breaking change or security.
A voter who sees the number knows the vote counted.
News your users can read, never news that nags them.
The widget draws into a container you place and takes your theme. Reading needs no account, and there is no popup and no badge.
It sits on your page like any other part of the page.
Write the release once. It shows up everywhere.
The widget is drawn from the cards you completed, so there is no second changelog to keep. Complete a card and it flows through.
So the page in your app and the page on the web never disagree.
How the changelog reaches votersWhat users notice once it is on your site
A product that looks alive
Fresh releases on the page tell visitors someone is building it.
Fewer questions about what is new
Support does not have to answer what changed, because the page does.
Proof that voting works
Each item shows how many people asked, so voters see their request matter.
Nothing extra for you to write
The entries come from cards you completed, so the widget costs no effort.
Your changelog on your site in three steps
It takes a few lines on your page, and you never touch it again.
Place a container on the page
Add an empty element where you want the changelog to appear.
Load the widget script
Add the script with your project slug and your public embed key.
Complete a card to see it appear
Move a card to Completed, publish the release and it shows in the timeline.
What people ask before they embed a changelog
How many releases load at first?
Five, newest first, with a show more button for the rest.
Can visitors read it without an account?
Yes. Reading needs no account.
Can I label each item?
Yes. An item can be new, an improvement, a fix, a breaking change or security.
Will it match my site?
It draws into your container and takes your theme, so it looks like part of your page.
Is there an unread badge?
No. There is no unread badge and no popover.
Do vote counts show?
Each item shows how many people asked, unless you hid vote counts on the board. Hidden counts stay hidden here.
Which plan has the widget?
Every plan, from Lite at $9/mo.
Do all visitors see the same releases?
Yes. Every visitor sees the same list.
Do I need to write the entries by hand?
No. They come from the cards you completed, so there is nothing to retype.
Does it work inside an iPhone app?
The widget draws into a web page. In an iPhone app, the Swift package can read the same changelog.
What you should know first
- There is no unread badge and no popover.
- Every visitor sees the same releases.
- Vote counts hidden on the board are hidden here too.
Where your next page is
Pages that work well beside a changelog on your site.
Tell users what shipped, where they are
On every plan from $9/mo. Both plans start with a 14 day trial of Pro, and a card is asked at signup.