Paragraph and heading nodes store their alignment under textAlign; button
and logo nodes used a bespoke alignment attribute instead, flagged with two
`@TODO: Update the attribute to textAlign` comments in renderer.tsx. Any
content built or imported using the rest of the editor's own textAlign
convention (e.g. programmatic template generation) would have its button/
logo alignment silently ignored and fall back to the hardcoded default.
Both render methods now prefer attrs.textAlign and fall back to the legacy
attrs.alignment, so older saved templates keep rendering exactly as before
while new/imported content can use the same attribute name as every other
aligned node. Only renderer.tsx changes - the Tiptap node schemas
(ButtonExtension, etc.) still read/write `alignment` for the live editor UI,
so there is no risk of the editor dropping an old template's alignment on
load.
Added 5 renderer tests (apps/web/src/lib/email-editor-node-alignment.unit.test.ts,
the only place in this repo with test infra for the EmailRenderer, matching
the existing campaign.unit.test.ts pattern) covering textAlign, legacy
alignment, and the default for both node types.
Closes#2.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>