What's New at Changebot

This morning we gave you four new designs. We buried the lede.

The design is one of three new improvements we've made with our hosted changelogs. The other two are the fonts your page is set in and the colors it is painted with, and if you have not touched either, your changelog is currently wearing last season's outfit. Time to fix that.

An improved design editor

Design editing has its own full-page editor now: Destinations → your changelog → Design → Edit design.

Controls on the left — design, heading font, body font, theme, six colors. You can preview your actual changelog with your actual updates, repainting the instant you make a change. Flip the preview between desktop and phone with one toggle.

Fonts, and curated font pairings

Your page contains two fonts: one for headings and one for body copy. You can now customize them. Pick from 20 heading fonts, and each one is paired with up to eight body fonts that we've curated.

So yes, you can absolutely ruin your changelog — but not with typography.

Here are all 20, each set in itself, next to the first body font on its list:

The font stack is independent of the design and the color palette. So you can experiement with different designs, colors, or fonts to find the perfect changelog for your product.

Additionally, we include fourteen fonts that are only available as body fonts: Public Sans, Source Sans 3, Figtree, Hanken Grotesk, Nunito Sans, Source Serif 4, Literata, Newsreader, Crimson Pro, Piazzolla, Roboto Serif, Roboto Mono, Source Code Pro and System mono.

That is 34 in total. Thirty-one are variable fonts we host ourselves, subset to Latin and stripped down to the weight axis — nothing phones Google at load time, and a visitor downloads exactly the one or two very small, stripped-down files your page uses. The last three are system stacks, which ship nothing at all and use whatever the reader’s device already has.

Seventeen palettes that you can use with any design

A palette is six colors: page, panel, highlight, text, accent, link. Everything else the page paints — body copy, dates, hairlines, the ink on a button, link hover — falls out of those six on its own.

Six of them were drawn for a particular design and show up when you switch to it. But that's just a suggestion. Go wild if you want. Console in Rose? Go ahead. Bento in Terminal? That's cool with us.

All seventeen clear 4.5:1 contrast for body text and links against the fill they sit on.

Or bring your own six colors

You can create your own color palette if you want as well!

Use one of ours as a starting point to make your own. Your version saves as a theme your team owns and lands in the picker in your own group, above ours. Edit a theme you already own and it saves in place, and every changelog pointed at it updates. Set your brand colors once, use them everywhere.

Your agent can do all of this too

Driving Changebot through MCP? Ask your agent to create a theme that matches your marketing site. It has all the tools it needs:

• list_fonts hands over the pairing table, so an agent knows which body fonts go with a heading font before it commits.
• list_themes returns your themes and ours, colors included.
• create_theme and update_theme write a palette your team owns.
• update_destination sets the design and both fonts. Pass "default" for a font to fall back to the design’s own pair.
• preview_destination renders any combination you like at a link you can open, saving nothing.

We're excited to introduce a new Automation that allows you to configure automated periodic recaps for your products. A "periodic recap" is just a customer update we write on a regular cadence — every day, every week, or every month — based on the frequency you pick. Think of it as a short, regular summary of what's changed that you can send to customers automatically.

This feature makes it easier than ever to keep your customers informed. The system automatically collects data such as merged pull requests, notable commits, and tickets to generate a polished update.

Where the recap goes is up to you. You can send it to your inbox for review first, or publish it directly to any destination — Slack, Discord, your hosted Changelog, or anywhere else you communicate with customers.

• Example: Send a private Slack message to customer-success once a month for manual review.
• Example: Publish weekly recaps straight to your hosted Changelog without manual steps.
• Example: Deliver daily summaries to a channel in Discord for an internal engineering channel.

Setting up these recaps is simple. This is an additional Automation available in the automation form — choose the 'Periodic Recap' option when creating or editing an automation, select the product, and pick the desired cadence. You can add it alongside other automations for the same product.

We hope this helps you keep customers in the loop with almost zero effort — spend less time writing updates and more time building great things.

• Save time — reduce the manual work of drafting and publishing update notes.
• Stay consistent — generated updates follow your style and can be previewed before sending.
• Keep control — set flows to draft for review or auto-publish once they meet your criteria.
• Send updates where they belong — to the Inbox for review, or to any destinations, like Slack, Discord, or your hosted changelog.

• Brand icons now appear across publication views so you can scan destinations at a glance.
• Destination and integration dropdowns are now alphabetized.
• “Webflow Integration” is now labeled “Webflow Site.”

• Generate channel-specific variants (X, LinkedIn, etc.) with appropriate tone, length, and formatting.
• Let you edit any generated variant in a simple editor.
• Provide AI suggestions and a chat-based refinement option to iterate on wording.
• Support undo/redo while you edit.

• Create a Customer Update.
• Choose which channels you want editions for.
• Generate editions and review AI suggestions.
• Edit or refine each edition, then publish the versions you need.