How a release moves through Paperstick
The short version is on the homepage. Here's the full walkthrough: where each piece lives, what your team does, and what your customers actually see at the other end.
Two URLs, one product
There are two addresses you'll see in Paperstick. One is where your team works. The other is where your customers read.
paperstick.app: where your team works
Sign up, create changelogs, draft entries, publish, and invite teammates. Anyone publishing release notes lives here. Customers never need to.
whatsnew.app: where your customers read
Each changelog has its own short URL on this domain. Customers get a clean page, optional filters by type, an RSS link, and a permalink on every update. No login, no signup, no tracker wall.
See a real public changelog
We ship our own changelog the same way you will. Open it in a new tab and compare it with the mockups below. What you see is what you'd publish to.
What you see after you sign in
Your home base is a clean list of changelogs. Jump between products, copy a public URL, open a changelog to edit or add an entry. It's deliberately minimal. The work is writing the update, not navigating chrome.
Log in. Once you sign up, this list fills in with the changelogs you create. Each row shows the public URL and links straight to entries.
Changelogs
One per product or audience. Each lives at whatsnew.app/your-slug the moment you create it.
-
View
Paperstick
whatsnew.app/paperstick
-
View
Acme
whatsnew.app/acme
-
View
Demo Changelog
whatsnew.app/demo
The flow, three steps
Step 1
Create a changelog (one per product or audience)
Name it, pick a short URL. The hosted public page goes live at whatsnew.app/your-slug the moment you save. No DNS, no hosting setup, nothing to deploy.
- Run one changelog per product or audience. You're not capped at one. We don't charge per changelog.
- The public URL is yours immediately and stays put even if you tweak the name later.
Title Faster dashboard load times
Step 2
Write what shipped (in two minutes)
Open the editor, type the change in plain language, add an optional version, date, and type. Need a headline? Tap the AI suggestion button to draft one from your details, then edit it before you publish.
- Save as draft until you're ready. Publishing pushes the entry to the public page in real time.
- Rich text, images, and YouTube or Vimeo embeds work the way your team expects from a modern editor.
Step 3
Send people there
Link from your app, docs, email footer, onboarding, and social. Customers get a calm page that's always current. RSS for power users, filters when you have more than one type, and a permalink for every entry so support and sales can drop a link to one update.
- Wherever you already talk to users, drop the changelog link. That's how it becomes the 'what's new' link customers expect.
- Filters only appear when you have more than one kind of update. Otherwise the page stays a simple timeline.
Try the editor in your browser
No account, no signup. Type sample release copy on one side, watch the public page rebuild on the other. The fastest way to feel how the writing-to-publishing loop reads.
Ready to make your next release land?
Start free for 30 days. Publish your first update in under a minute. Customers see it the moment you hit publish.