HTML code editor
Use HTML Code when your team already has email markup or needs direct control over its layout and inline styles. Bring the HTML into the shared composer, connect the customer data and add personalization where it serves the message.
Your HTML defines the layout, while Liquid, any Adaptyle instructions and the sending footer are resolved during rendering. Test the result in representative email clients; this editor does not create responsive layouts for you. If you would rather have that handled for you, use the MJML code editor instead.
Write the subject and the body
The editor has two fields. Subject is a single line. Body HTML is the full markup, in a code area with line numbers and a minimap.
Both fields accept Liquid and Adaptyle, so the subject is personalized the same way the body is. The editor colors all three languages together as you type, and underlines Liquid that will not resolve against your sample data before you ever render a preview.
There is no auto-format here. Lay out your markup the way you want to read it, because maxclicks will not reindent it for you. The MJML code editor behaves the same way.
Set the sender and the recipient
From and To sit above the subject, the same as in every other editor. See the editor overview for what each one accepts.
Use your brand kit instead of hard-coded values
The brand kit you select in email setup arrives as branding, so write {{ branding.logoUrl }} rather than pasting the link. Colors and fonts come through the same way. References resolve when the email is rendered; sent emails and frozen broadcast content keep their existing values. See brand-kit changes.
Give every image a descriptive alt attribute. It is what screen readers
announce, and it is all your reader sees in the many clients that block images
by default.
Coming from the Plain Composer
The Plain Composer can hand its blocks over to this editor, written out as HTML.
That switch is one-way. Once the blocks are markup there is no way back to them, and maxclicks asks you to confirm before doing it.
Work within the email renderer’s limits
Use email-safe HTML with absolute resource URLs. Final rendering rejects active content such as scripts, iframes, forms, event-handler attributes and unsupported URL schemes. It also enforces size and structure limits: a nonempty single-line subject up to 4,096 bytes, a final HTML artifact up to 1 MiB, at most 6,000 elements and nesting no deeper than 80 levels.
During AI personalization, existing links, attributes, stylesheets and protected layout context must remain intact. Put prompts inside the text you want rewritten; change markup and destinations while authoring the draft. An “invalid final artifact” error requires fixing the content, even if a browser could display it.
The Outline, Personalize, Data and Checks tabs share the same behavior as the email editor. Ask maxinja to make a specific source edit, then render and send a test to review the compiled result.
Related
- Plain Composer: the block-based way to build the same HTML.
- MJML code editor: responsive layout without hand-writing tables.
- Sample data: what the preview renders against.