Release Notes Email Template — Version Number at Display Scale
A bold release-notes email with the version number at 96px display scale in the layout hero, a rule-divided change list, and a single CTA. Designed for SaaS product teams.
Preview unavailable — view the prompt below.
The prompt
Two ways to build this email in plain language. The fastest is Temway's in-editor assistant — open the chat drawer in the email editor and paste the recipe below. Or connect Claude or ChatGPT via Temway's MCP and paste it there; the agent builds the email step by step. Either way, adapt the copy and colors to your brand.
- An email is a top-to-bottom stack of blocks — the recipe follows that order.
- A
[layout]step becomes a single image (great for heroes); everything else stays live text and links. - Theme the footer to match — the recipe's last step does exactly that.
Want this exact email? Click Use this template below to clone
it into your workspace, then ask the in-editor assistant to rebrand it. Over MCP, tell
your agent to clone the Temway share -sT6Qqex7oymgjo5Jbo35 and rebrand. For the
full model, point an MCP agent at get_concept — email-structure,
layouts-vs-emails, design-recipes.
A product update email that leads with the version number itself. A layout hero sets “2.14” at display scale above a rule-divided list of three changes; a native section restates each change with a one-line explainer, a breaking-changes callout, and a single rose-coloured CTA. Designed to be scanned in five seconds.
Snapshot
- Goal: announce a version release and get developers to the full notes.
- Audience & tone: developers and product teams. Direct, technical, no marketing.
- Palette: page
#ecedee· container#ffffff· text#111827/#6c7079(muted) · accent#be123c - Font:
Helvetica, Arial, sans-serif - Artwork: free-form layout hero — Version announcement, centred: a tracked changelog label, the version number at display scale in tabular figures, a heavy rule, then the headline change on one line., 600×400 canvas. Everything below it is native, selectable, clickable.
Build recipe
Each step is one block in the flat stack, top to bottom.
[native]= a real email block.[layout]= a free-form layout embedded as a single image.
- [layout] Layout hero — build a free-form composition (600×400) via
create_layout+set_layout_content. Version announcement, centred: a tracked changelog label, the version number at display scale in tabular figures, a heavy rule, then the headline change on one line. Alt text: “A poster reading version 2.14 at display scale, above one headline change”. - [native] Headline — text. “Templates now include a sketch”, fontSize: 36, color
#111827, center. - [native] Standfirst — text. “Discovery payloads show the composition before you apply it, and masks now cover an arch or a circle.”, fontSize: 20, color
#6c7079, center. - [native] Primary CTA — button. Label “Read the full release notes”, fill
#be123c, color#ffffff, shapeStyle: ‘0_1’, center. - [native] Story title 1 — text. “Images can now mask to an arch or a circle”, fontSize: 20, color
#111827, center. - [native] Body copy 1 — text. “No more choosing between a plain rectangle and a hand-drawn custom SVG for a masked photograph.”, fontSize: 16, color
#111827, center. - [native] Story title 2 — text. “Countdown boards are now transparent”, fontSize: 20, color
#111827, center. - [native] Body copy 2 — text. “A coloured card no longer shows a dark box behind the numbers — the board now matches whatever sits beneath it.”, fontSize: 16, color
#111827, center. - [native] Body copy 3 — text. “Cloud workspaces are already on 2.14 — self-hosted upgrades follow the usual quarterly channel.”, fontSize: 16, color
#6c7079, center. - [native] Footer rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Footer social — social. Icon row, social.color
#be123c, style circle-outline, center. - [native] Footer address — address. Postal address + unsubscribe, address.color
#6c7079, address.fontFamilyHelvetica, Arial, sans-serif, center.
Make it yours
- Swap “2.14” for your version and rewrite the three change lines (in both the layout hero and the native detail blocks).
- Recolor the rose accent (
#be123c) to your brand — keep it on the kicker, the button, and the link only. - Replace the breaking-changes body with real migration notes, or drop the section if there are none.
About announcements email templates
An announcement earns its own send when it's time-sensitive or significant enough to need full attention on its own subject line — a launch, a leadership change, a funding round, or a policy update, rather than one more line in the next newsletter issue.
See all announcements templates →What kind of news deserves a standalone announcement email instead of a newsletter mention?
Anything time-sensitive or significant enough to need its own subject line and full attention — a launch, a leadership change, a funding round, or a policy update that changes how customers use your product.
How long should a product-update announcement be?
Long enough to explain what shipped and why it matters, short enough to read in under a minute — the templates below separate a short "what's new" summary from optional deeper detail below it.
How do I announce a leadership change without it feeling like a press release?
The new-CEO and leadership templates below lead with a short, human bio and a direct quote rather than a formal title-and-tenure rundown.
Should an announcement email include a call to action?
Not always — a policy update or leadership announcement can stand on its own, while a product-launch announcement should point to one clear next step, like trying the feature or booking a demo.