Do I need to know MJML to use else.events templates?

No. else.events provides a template editor for common edits — copy, CTA text, layout adjustments. MJML knowledge is useful for custom template designs but not required for everyday editing.

Does else.events support custom HTML email templates?

Yes. You can bring your own HTML templates. MJML is the recommended format for cross-client compatibility, but raw HTML templates are also supported.

Can non-developers edit email templates in else.events?

Yes. The editor is designed for copy and layout changes that do not require code. Developers handle template creation; non-developers handle ongoing copy edits.

How do template variables work with MJML?

Template variables use a {{ variable }} syntax in MJML source. else.events injects values from the event payload at render time. The rendered HTML is what gets sent to the email provider.

Templates that work in every email client

MJML-based email templates — responsive by default, editable without a deploy

else.events uses MJML as its template foundation. Write once, render correctly in Gmail, Outlook, Apple Mail and mobile clients. Edit copy and layout in the else.events editor — no code change, no deployment.

Build your first MJML template See headless email CMS

Why email templates are painful without MJML

HTML email CSS is a compatibility nightmare

Email clients do not agree on CSS support. What renders in Gmail breaks in Outlook. Responsive email without a framework means writing CSS for a dozen rendering engines.

Templates hardcoded in code cannot be edited without a developer

A marketing manager who wants to change a subject line or CTA copy needs a developer, a PR and a deployment — for a sentence.

No preview before sending means surprises in production

Sending a test email to check rendering is slow. Without a preview system, broken templates reach real users.

Reusing headers, footers and brand elements across templates is fragile

Copy-pasting header blocks across templates means every brand update touches every template file.

MJML foundation, visual editor, reusable blocks

MJML-based templates — responsive out of the box

Templates are built on MJML. The result is HTML that works in every major email client without per-client CSS hacks.

Edit in the else.events editor — no deployment

Change subject lines, CTA copy, body text and layout in the else.events template editor. Changes go live immediately. Developers not required for copy changes.

Preview before sending

Preview rendered templates in the else.events dashboard before assigning them to a rule. Catch layout issues before they reach users.

Brand variables and reusable blocks

Define brand colours, logo URLs and footer text as brand variables. Use them across all templates. Update once — all templates reflect the change.

Frequently asked questions

Do I need to know MJML to use else.events templates?: No. else.events provides a template editor for common edits — copy, CTA text, layout adjustments. MJML knowledge is useful for custom template designs but not required for everyday editing.
Does else.events support custom HTML email templates?: Yes. You can bring your own HTML templates. MJML is the recommended format for cross-client compatibility, but raw HTML templates are also supported.
Can non-developers edit email templates in else.events?: Yes. The editor is designed for copy and layout changes that do not require code. Developers handle template creation; non-developers handle ongoing copy edits.
How do template variables work with MJML?: Template variables use a {{ variable }} syntax in MJML source. else.events injects values from the event payload at render time. The rendered HTML is what gets sent to the email provider.

MJML templates that work everywhere, editable by anyone

Responsive by default, editable without a deploy, previewed before sending.

MJML for cross-client compatibility
Edit without deployment
Brand variables across all templates