Publishing releases
Publish big launches as full release pages and smaller updates to the rolling Latest feed — then keep everything current without ever re-deploying.
Releases vs the Latest feed
The Update Center gives you two ways to publish, and most teams use both:
A release
A page of its own, with its own URL. It appears on the calendar, in search, and in tag filters, and it can lead with a Spotlight hero. Use releases for launches and anything worth linking to.
The Latest feed
A rolling, no-page release. Fixes, tweaks, and quality-of-life improvements appear in the feed without a dedicated page — publish them in seconds and move on.
Creating a release
Releases are created and managed from the Update Center section of the DemoBites dashboard:
- 1
Create a release
Start a new release and give it a title that says what shipped.
- 2
Add your content
Bring in the bites that show the change and write the story around them.
- 3
Add a Spotlight hero (optional)
Lead the release with a rendered Spotlight video for launches that deserve a hero moment.
- 4
Tag it
Tags power the public filters, so visitors can browse by the areas they care about.
- 5
Publish
The release goes live on its own page immediately — on the calendar, in search, and in the filters.
Publishing never emails anyone.Release emails only go out when you explicitly hit “Notify subscribers” — see Subscribers. Publish as often as you like.
Version labels & backdating
Releases carry the metadata your visitors expect from a changelog:
Version labels
Give a release a version label so it reads like your release train — visitors see it on the release page and in the feed.
Backdating
Set the release date to the day it actually shipped. The calendar and the ordering of the feed honor the date you choose, so you can fill in history after the fact.
The calendar
The public calendar shows one or two months of releases at a glance. Days with a release are highlighted, and visitors can jump from a day straight to what shipped. Because it honors release dates — including backdated ones — the calendar doubles as a live record of your shipping momentum.
No minimum-content rules
There is no minimum amount of content required to publish. A single release — or a single Latest-feed update — is enough to take your Update Center live. Publish when you’re ready, and let the page grow with every release.
Updating after publish
Releases stay editable after they go live. Fix a typo, swap a bite, add a video, or adjust tags — your changes appear on the same URL as soon as you save. Nothing is frozen at publish time.
Edits are quiet
Editing a published release never re-sends its email. Sending is always an explicit action, so you can polish freely after launch.