Lifecycle
For reusable email sections that support product, customer, and operational messages.
Production block
Single-action dark CTA block used to close campaign sections.
Use as the primary action after a hero, proof block, or information section.
After the decision point, where the reader needs a clear next action.
To reuse a production-tested email section without starting from a blank file.
Preview
Rendered production artefact for workflow review before handoff.

Treat the component as one production section inside a larger message system. It should support the send goal, survive handoff, and remain easy to review before compilation.
For reusable email sections that support product, customer, and operational messages.
These relationships help buyers understand the block as part of a send, not as an isolated catalogue item.
Keep the checks short and action-oriented. The goal is to help teams decide whether this block is ready to enter a workflow.
A production email usually needs a stack of blocks. These nearby sections are a sensible next choice when assembling a full send.
Large single CTA block for closing announcement, newsletter, and lifecycle sections.
Two side-by-side call-to-action buttons for comparison or primary and secondary actions.
Badge-style CTA chip for labelling exclusive access, member perks, or premium email sections.
Source stays below the preview and workflow context. Copy MJML when assembling a system, or compiled HTML when preparing ESP handoff. Template Hedgehog Pro includes the full offline archive for teams that need the complete system locally.
Block assembly: place this section inside the same <mj-body> as your other production blocks, then stack sections in send order.
Editable source
Section-only MJML for assembling an email from multiple reusable production blocks inside a shared project.
Formatting code preview...Compiled output
Component-only compiled markup for block-level inspection and HTML assembly workflows.
Formatting code preview...