Goal
Keep stakeholders informed with scannable updates that can be repeated reliably.
Template Hedgehog
Open navigation
Weekly reporting digest
Share recurring product or campaign performance updates using a stable digest structure.
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 on a schedule to report weekly performance or operational metrics.
Layout
Weekly Digest 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.
report.period_label
Time window shown in the heading.
report.top_metric_value
Primary KPI surfaced near the top.
report.dashboard_url
Destination for full report details.
Variant routes
- Low engagement reminder: Adjusts the opener when report readership drops below target.
- Executive summary version: Reduces module count for leadership audiences.
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
Weekly Digest System
Weekly digest layout combining a stacked list, multi-article grid, and newsletter footer for recurring editorial sends.
Component stack
Header Centred, Weekly Digest List, Multi-Article Newsletter Grid, Footer Social Light
Source file
weekly-newsletter.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
- Dense metric rows become hard to scan if spacing is reduced in editor overrides.
- Image-heavy report cards can exceed weight limits in some ESP send pipelines.
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.