Source and output stay together
The sample includes editable MJML and compiled HTML so buyers can inspect the real source-to-handoff model before paying.
Template Hedgehog
Open navigation
Inspect the sample pack before buying.
Download one complete public workflow sample from Template Hedgehog v1.0.1, last updated 19 May 2026. It shows the artefact style, folder structure, source files, compiled output, QA notes, implementation guidance, and licence context before you choose Core, Pro, or Team.
Public sample contents
README.mdWhat the sample is, what it is not, and how to inspect it.
layouts/sample-onboarding-system/source.mjmlEditable MJML source for one complete workflow sample.
layouts/sample-onboarding-system/compiled.htmlCompiled HTML generated from the included MJML source.
layouts/sample-onboarding-system/qa-notes.mdPractical review notes for copy, links, images, mobile, and ESP handoff.
layouts/sample-onboarding-system/implementation-guide.mdStep-by-step implementation route from source to platform upload.
layouts/sample-onboarding-system/testing-proof.mdWhat to test locally and what still needs ESP seed testing.
workflows/sample-onboarding-workflow.mdWorkflow context, trigger, fields, variants, QA risks, and handoff notes.
docs/archive-structure.mdHow Core, Pro, and Team archives are organised.
docs/licence-reference.mdPlain-language summary of tier fit, rights, and update windows.
What the sample proves.
The sample is designed to answer the practical buyer question: will the paid archive be easy to inspect, adapt, QA, and hand off?
QA is part of the package
The sample includes QA and testing notes rather than treating rendering, links, images, and platform handoff as afterthoughts.
The archive is structured for use
The folder structure mirrors the paid archive model: source, output, workflow notes, implementation guidance, and licence context stay connected.
What the sample is not.
The sample should reduce uncertainty without blurring the paid licence or implying Template Hedgehog replaces your sending platform.
The sample pack is public inspection material, not the paid Core, Pro, or Team archive.
The sample includes one onboarding workflow, not the complete component, layout, or workflow set.
Sample copy, links, sender details, images, merge fields, and legal text must be replaced before production use.
Your ESP still handles audiences, consent, unsubscribe, automation, delivery, reporting, and final seed testing.
Inspect the sample, then choose the archive.
Use the sample to check source quality, compiled output, QA notes, and handoff structure. Buy Core for the starter system, Pro for recurring production, or Team when reuse rights and support matter.