Source-to-Sent Email Mismatch

This is the core pain of email development, the code a team writes is often not the code that actually gets tested or sent. Podia wrote simple HTML and CSS, then used Roadie to rewrite it into inline styled email HTML for older clients like Outlook. That made quick experiments possible, but it broke the feedback loop, because any fix made in Litmus had to be recreated in the original source and compiled again to know it would really stick.

• Podia was building an email builder, not hand coding one campaign at a time. That meant the real job was stabilizing the generation system underneath many template variations, so testing the compiled output mattered more than editing raw code in Litmus.
  1 sacra
• This workflow looks a lot like GitHub's older internal email system and Figma's process. Teams author reusable source files, then a tool expands them into full HTML with inline styles. The benefit is one change can update many emails. The cost is another translation step where bugs can hide.
  3 sacra
• It also explains why Litmus and Parcel serve different jobs. Litmus is strongest as a screenshot and inbox preview layer. Parcel and local editors are stronger as the place where developers work on source files, run checks, and manage reusable components before compilation.
  1 sacra 4 sacra 5 sacra

The direction of travel is toward tools that collapse these steps into one workspace, where source files, compilation, preview, QA, and version history stay connected. As creator platforms add richer email products, the winners will make email code feel less like pasting artifacts between tools and more like shipping normal software.