Hermod Mail is pre-v0.1 — release acceptance is still in progress Read the release status →
Par avion · established MMXXII

Email components
that arrive intact.

A Laravel-native library of re-brandable transactional email components and templates, with provider-neutral HTML and plain-text output.

Read the setup guide
8 Core templates·61 Pro templates·pre-v0.1
// app/Mail/OrderReceipt.php
use Jml\HermodMail\Mail\OrderReceiptMail;
Mail::to($customer)
  ->send(new OrderReceiptMail($data));
Laravel Mailable → HTML + text ✓ provider-neutral output
LARAVELBLADEMAILABLESSTUDIOTHEMINGHTMLPLAIN TEXTOPEN CORE

Everything in the mailbag

Section 01 — Features
01

Sixty-nine templates

Eight MIT Core templates and 61 separately licensed Pro templates share one catalog contract.

02

Outlook-aware output

Maizzle button output includes conditional MSO spacer markup, while Hermod templates use table-based email structure.

03

Dark mode pairs

Declare one colour, get its dark counterpart. Handles Gmail colour inversion and Apple Mail overrides.

04

Brand profiles

One profile governs identity, palette, status colours, radii, company details, and reviewed links.

05

Reviewable accessibility

Semantic structure and text alternatives are review concerns today; an automated brand contrast preflight remains planned work.

06

Subject localization

Laravel subject translations ship today. Locale-specific body and preheader artifacts are intentionally deferred beyond pre-v0.1.

The sorting office

Section 02 — Workflow
STEP 01

Compose

Create a Laravel Mailable with typed Hermod data and brand tokens.

STEP 02

Frank

Compile to table HTML plus a plain-text twin in one command.

STEP 03

Inspect

Review HTML and plain text locally; stable release still requires the documented client matrix.

STEP 04

Dispatch

Send the Mailable through the transport configured by your Laravel application.

LIVE PREVIEW SERVER

Hot-reload every template at localhost:5111, with device widths, dark-mode toggle and a plain-text pane side by side.

LOCAL BRANDING

Review product name, logo, palette, links, and layout tokens in Studio before synchronizing them into Laravel.

RELEASE GUARDRAILS

Source, package, Studio, and consumer tests run in CI. The documented real-client matrix remains required before stable release.

Client acceptance targets

Section 03 — Compatibility
Client Dark mode Web fonts Responsive Status
Gmail (web, iOS, Android) Token strategy Fallback stack Media queries Acceptance pending
Apple Mail / iOS Mail Token strategy Web fonts Media queries Acceptance pending
Outlook Windows Static palette Fallback stack Ghost tables Acceptance pending
Outlook web Token strategy Fallback stack Media queries Acceptance pending
Product contract

Open Core for Laravel email

Eight MIT Core templates establish the engine; 61 Pro templates extend the catalog under one-time licenses.

Read the contract
8
MIT Core templates
61
Pro templates
69
Templates total

“The package ships provider-neutral Laravel Mailables and typed data contracts.”

Core product contract

“Studio previews, themes, and exports locally without owning production delivery.”

Studio product contract

“Real-client release acceptance is still required before the first stable tag.”

Release evidence

Build Laravel email locally

Start with eight MIT Core templates. Pro licensing and stable release are still prelaunch.

Docs Contact