Document dark mode support for email layouts

[samseely]

Summary

• Add a new "Dark mode support" subsection to content/integrations/email/layouts.mdx under Custom layouts and styling.
• Explain that layouts created on or after April 21, 2026 support dark mode by default, and call out that legacy default layouts do not — with two remediation paths (create a fresh layout, or update the existing one).
• Document the three pieces the default layout uses to opt in: color-scheme meta tags, the color-scheme CSS property on :root, and the @media (prefers-color-scheme: dark) block, with a minimal drop-in snippet.
• Document the light/dark image swap pattern using vars.branding.dark_logo_url / vars.branding.dark_icon_url plus the .light-img / .dark-img classes and the <!--[if !mso]> Outlook conditional.
• Add a callout noting that clients without prefers-color-scheme support fall back to light mode styles.

Test plan

• Run yarn dev and confirm the new section renders under Custom layouts and styling on /integrations/email/layouts.
• Verify the MDX code fences (including the Liquid {% assign %} snippet) render without breaking the page.
• Verify both Callout components render with the correct variants (alert + note).
• Check that in-page anchor links to surrounding sections (e.g., the per-tenant branding and workflow-run scope sections) still resolve.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Apr 21, 2026 4:02am

[cursor]

Risk LOW: Adds a new "Dark mode support" subsection to the existing email layouts documentation page with code examples for color scheme meta tags, CSS media queries, and logo swapping.

Reasons

• Only one file changed: content/integrations/email/layouts.mdx (content-only MDX)
• No component, layout, library, or style .ts/.tsx files are modified
• No new pages added, no sidebar or navigation changes
• No package.json, yarn.lock, or build configuration changes
• Pure content addition (117 insertions, 0 deletions) to an existing page with no structural refactoring

Notes

• Verify the Liquid template syntax ({% assign %}) renders correctly inside MDX code fences
• Confirm the Callout component props (type="alert" and emoji="🌠") match the expected component API
• Check that the in-page anchor links to surrounding sections (e.g., workflow-run scope, pre-content variables) still resolve after the insertion

  

_{Sent by Cursor Automation: Docs PR classifier}