Upgrade the compose editor from plaintext to rich HTML with formatting, send messages as multipart/alternative, and add signatures. The reader already renders HTML; this brings
composition to parity.
Spec
The compose editor should support HTML rich email content and offer rich formatting support
(and signatures).
Users can format text; sent mail carries both an HTML part and a plaintext fallback;
signatures insert per their rules.
Notes
#23 (rounded corners) is folded into #36. Choose a Compose-compatible, GPL-compatible
rich-text approach.
## Summary
Upgrade the compose editor from plaintext to rich HTML with formatting, send messages as
`multipart/alternative`, and add signatures. The reader already renders HTML; this brings
composition to parity.
## Spec
The compose editor should support HTML rich email content and offer rich formatting support
(and signatures).
## Breakdown
- [ ] #36 — rich-text (HTML) editor + formatting toolbar (absorbs #23 rounded corners)
- [ ] #37 — multipart/alternative send (text/html + text/plain) + reply/forward quoting
- [ ] #38 — signatures (per-account, auto-insert, HTML)
## Acceptance criteria
- Users can format text; sent mail carries both an HTML part and a plaintext fallback;
signatures insert per their rules.
## Notes
#23 (rounded corners) is folded into #36. Choose a Compose-compatible, GPL-compatible
rich-text approach.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Upgrade the compose editor from plaintext to rich HTML with formatting, send messages as
multipart/alternative, and add signatures. The reader already renders HTML; this bringscomposition to parity.
Spec
The compose editor should support HTML rich email content and offer rich formatting support
(and signatures).
Breakdown
Acceptance criteria
signatures insert per their rules.
Notes
#23 (rounded corners) is folded into #36. Choose a Compose-compatible, GPL-compatible
rich-text approach.