Goal
Drive awareness and feature adoption with production-safe launch messaging.
Template Hedgehog
Open navigation
Feature announcement
Launch new capability updates with reusable structure that keeps messaging and CTA order consistent.
Workflow assembly
Trigger to production output
01
Trigger
Real send event
02
Workflow
Message journey
03
Layout
Complete structure
04
Components
Reusable blocks
05
Production output
Workflow structure
Sent when releasing notable product updates.
Layout
Feature Announcement System
Pro archive
This workflow is part of the Pro archive. Use it when this send is recurring enough that source ownership, QA notes, variants, and handoff context matter more than a one-off template.
Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.
What the production package needs.
A workflow is useful when the implementation contract is visible before anyone starts editing markup.
feature.title
Primary release heading.
feature.value_points
Short list of benefit lines used in content blocks.
feature.learn_more_url
Destination for full release context.
Variant routes
- Private beta invitation: Invitation-led variant with access request CTA.
- General availability release: GA variant with migration or rollout guidance.
Package access
- Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
- Full MJML source for this workflow
- Compiled HTML output ready for ESP upload
- Variant-ready workflow pack files
- Versioned workflow updates inside Template Hedgehog Pro
Linked production layout
Feature Announcement System
Product update email combining a feature split hero, usage proof, CTA reinforcement, and app-safe footer content.
Component stack
Header Centred, Feature Announcement Split, Statistics Trio, Primary CTA Button, Footer App Legal
Source file
feature-announcement.mjml
QA and handoff.
The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.
QA risks to review
- Feature names and supporting stats can overrun headline areas in translated locales.
- Release imagery should be optional for clients that block remote assets by default.
Handoff steps
- Edit copy and block order in MJML, keeping utility and footer sections unchanged unless requirements demand it.
- Compile MJML to HTML and run client checks in Gmail, Outlook Desktop, and Apple Mail before handoff.
- Import compiled HTML into the ESP, map merge variables, and send an internal seed round for QA sign-off.
Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.
Use this workflow inside Pro.
Pro is the archive for teams that keep rebuilding production emails and need repeatable workflows, editable MJML, compiled HTML, QA notes, implementation guidance, and updates.