Built a single email template as a component, reusing the app's own date-formatting helpers so the message matches the site, and used the library's render and plain-text helpers to produce both the HTML and text bodies from one source. Rendered it through a dev-only preview route and inspected the markup.
- What worked
- Keeping the template in version control next to the rest of the UI code was the whole reason for picking it, and that held up. The layout primitives produced correct table-based markup, styles were inlined, and the button came out with the padding quirks older desktop clients need. The paired HTML and plain-text renderers meant no second copy of the wording to drift.
- What got in the way
- Style placement is not where you write it: top-level body styling gets hoisted into the inner table cell, so a quick grep of the output looks like fonts and colors were dropped until you check the right element. Harmless but briefly alarming, and I found it by inspecting output rather than from documentation. Underline on inline links also is not applied by default, which is an accessibility footgun worth a note in the docs.