Emails
The editor
Canvas, blocks, design, preview, footer, and Ask AI.
Every Audryo email — Journey step, campaign, transactional template, or library draft — opens in the same editor. This page is the operator map of that canvas: what each surface does, how drafts become live, and the rules that keep mail sendable.
Layout
The editor has four working areas:
| Area | What it is for |
|---|---|
| Canvas | The email itself. Click text to edit. Drag blocks from the palette. Toggle Preview for delivery HTML, Mobile for a narrow viewport, and Text for the plain-text part. |
| Left sidebar | Add content (section templates and blocks) and Email structure (outline, conditional visibility). |
| Right sidebar | Design (brand colors, type, spacing, logo width), sender overrides, and per-block settings when something is selected. |
| Top bar | Internal name, locale, Save draft / Confirm, Send test, Ask AI. |
The internal name is not the inbox subject. Recipients see subject and preheader. Keep the name short so the Content library stays scannable.
Draft vs confirm
| Action | What happens |
|---|---|
| Save draft | Updates the working revision (proposed). Live Journeys and campaigns keep using the last confirmed version. |
| Confirm | Publishes a new immutable version. This is what actually sends. |
| Send test | Delivers one copy to an address you choose. Marked as a test. Does not enroll anyone or count as a campaign send. |
Past confirmed versions stay under the email’s history. You can inspect an older version; restoring it creates a new revision rather than rewriting the past.
A Journey or campaign never sends an open draft. If a step is missing a confirmed variant in an enabled locale, Review lists it as a blocker.
Content you can add
Section templates
Pre-built layouts you drop as a group, then edit:
Welcome note, Next step, Hero spotlight, Launch announcement, Announcement bar, Image + text, Text + image, Feature cards, Three-up features, Numbered steps, Stats strip, Customer quote, Story + proof, Digest list, Update cards, Agent note, Offer band, Focused CTA, Soft invite.
Use these when you want a complete module (heading + proof + action), not a single line of type.
Content blocks
Heading, paragraph, button, image, logo, icon, columns, section, divider, spacer, quote, bulleted list, numbered list, link card, code, repeat / line items, footer.
Slash (/) on an empty line opens the same block menu as the palette.
Repeat / line items is for arrays in data (receipts, digest rows). Bind the block to an array field, then put merge tags inside the repeating row. See Personalization.
Code is for a short snippet the reader should copy (an API key shape, a CLI command). It is escaped in the rendered HTML — it is not a place to paste raw email HTML.
Saved sections
Reusable fragments your team saved from an email. Editing a saved section can be pushed to every email that still uses that fragment. Check usages before you push.
Design
Design controls apply to the open document’s emailStyle. Typical controls:
- Body, heading, and muted text color
- Button fill and button text
- Canvas / card background
- Font family (including Google Fonts the renderer can load)
- Body size, heading size, line height, content padding
- Logo width (S / M / L / XL map to 80 / 120 / 176 / 240 px)
- Icon color (icons inherit this unless you override a single icon)
Push styles applies the current look to other drafts and templates in the project. Confirmed emails stay frozen — they keep the style they were confirmed with.
The brand base template under Emails → Templates is the default look for new emails. Changing it does not rewrite already confirmed mail.
Per-email From & replies overrides the project sending identity for that document only (from name, from email, reply-to, CC/BCC). The domain must still be the verified sending domain.
Preview
Preview renders the same HTML your ESP will send (merge tags filled with sample or selected-contact data). Mobile is a width constraint, not a second document. Text is the auto-generated plain-text part clients use when HTML is off.
Icons that look broken in the canvas but correct in Preview usually mean the editor is still resolving an audryo-icon: source — reload the email if a newly inserted icon stays on the error placeholder.
Images and icons
- Photos must come from Images (project assets). Do not paste
random CDN URLs; they will fail lint or disappear later.
- Logo is the brand wordmark. Size it from Design, not by stretching
a square favicon.
- Icons pick from the bundled set (Lucide, Phosphor, Heroicons, and
others). Color follows the theme unless you set a per-icon color.
Footer
Every marketing and newsletter layout includes a footer with identity, preferences, and unsubscribe. Audryo injects the project footer template at send time so you cannot “forget” the link. You can still write a closing line *above* that legal footer.
Edit the default footer copy under Settings → Email delivery (project footer settings). Locale-specific templates are supported when the project has more than one content language.
Ask AI
Ask AI revises the open draft from a written instruction. It cannot confirm, activate, or send. Claims about the product must match confirmed Foundation facts — the model is not allowed to invent pricing, legal, or “you’re done” copy. Review the proposal like any other draft.