Documentation Index

Fetch the complete documentation index at: https://help.elaine.io/llms.txt

Use this file to discover all available pages before exploring further.

Responsive email templates

Prev Next

Responsive email templates provide a reliable framework for messages that must remain usable across screen sizes, inbox applications, and client-specific rendering engines. In Elaine, templates combine controlled structure with editable articles, fallbacks, analysis, and advanced device-specific or interactive experiences.

Template foundations

     
  • A framework template defines document structure, editable regions, branding, responsive behavior, and technical defaults.
  •  
  • Email markup must account for uneven HTML and CSS support across email clients.
  •  
  • Mobile-first hierarchy, readable type, touch-friendly actions, meaningful alt text, text alternatives, and robust fallbacks improve usability.
  •  
  • Reusable articles and widgets should be tested with short, long, missing, and highly personalized content.

Message Analysis

Elaine's Message Analysis helps identify and remove potential error sources before release. It complements editorial review and visual testing by checking configured aspects of the message, its structure, and content. Treat analysis findings as part of template quality assurance, then repeat the affected checks after making corrections.

Ultra Responsive content

Ultra Responsive templates can go beyond client-side CSS. Elaine can use server-side image and link switching to serve device-specific assets or destinations when a message is opened or a link is selected. This allows template engineers to optimize content for device contexts even where email-client capabilities are limited. Because detection and fallback behavior affect the result, these variants must be designed and tested explicitly.

Interactive messages

Elaine also supports interactive email experiences such as ratings, surveys, quizzes, timers, video, and dynamic content in supported clients. Every interactive component needs a useful fallback for clients that cannot render or execute the enhanced experience. Keep the primary action understandable and accessible in both versions.

Build and release

     
  1. Define supported modules, widths, responsive behavior, typography, colors, accessibility requirements, and client coverage.
  2.  
  3. Build with email-compatible structures and create fallbacks for unsupported styles, media, and interactions.
  4.  
  5. Use Message Analysis to locate configured structural or content-related error sources.
  6.  
  7. Test representative content extremes and personalized variants.
  8.  
  9. For new or changed templates, use automated email-client screenshots to compare rendering across the supported programs and devices.
  10.  
  11. Version and release the template through controlled change and approval processes.

Note

Exact UI labels, analysis rules, client coverage, and advanced template capabilities can depend on the Elaine.io release, licensed capabilities, permissions, and project configuration.