Backend/emails: Review copy before localizing#9150
Conversation
MobileInstall the Dev Tool (iOS via TestFlight, iOS Simulator, or Android .apk) here. Scan the QR with your phone camera, or tap Open in Dev Tool on the device, to open this branch in the installed Dev Tool dev client.
Deep linksiOS Android Web (Vercel)View the Vercel web preview for this branch. Backend
Other
|
f3f3462 to
263f3ff
Compare
jesseallhands
left a comment
There was a problem hiding this comment.
mostly some wording improvements
c568ab5 to
ea7df78
Compare
Co-authored-by: Jesse <79384268+jesseallhands@users.noreply.github.com> Co-authored-by: Tristan Labelle <github@tristanlabelle.com>
Co-authored-by: Jesse <79384268+jesseallhands@users.noreply.github.com>
5e3b579 to
594fc41
Compare
jesseallhands
left a comment
There was a problem hiding this comment.
left some replies in there; we definitely need new issues for mod note and postal verification rewording. Please tag me in both those issues and I'll also discuss with Aapeli.
|
@jesseallhands thanks. I added the "my home" reference and will merge. Then I'll follow up with the updated onboarding1 message PR, and we have ongoing convos about the postal verification and moderator note renames. |
📝 Release NotesThis PR does not need to be included in release notes. Reason: This PR mainly rewrote and standardized email copy in preparation for localization, with only minor user-visible wording tweaks and a small quick-decline addition to reminder emails. It is mostly editorial/internal cleanup rather than a significant new end-user feature or major technical improvement. 🤖 Bot Debug InformationModel: |


Emails are about to be exposed for localization so I reviewed our copy holistically to improve it and make it more consistent, as to minimize chances we'll want to tweak the text once that means new work for 10+ translators.
This is by nature quite editorial and hard to do by committee. I wrote the principles I followed so in the emails.py header, where possible, please suggest improvements there rather than on specific instances.
Until CI kicks in, you can review all emails as HTML files here: https://drive.google.com/drive/folders/12HVJ-Gyt-LJCrwQQlXJ4ui6OzDVBA5cb?usp=sharing
The only email I haven't touched is the first onboarding reminder email. It's quite long and could be made more concise, but I didn't want to give it my voice since it's signed by Aapeli.
I also found that we have a first email asking for a reference that says "How was X's stay with you?", a friendlier tone than the "You have X days to write a reference" reminder emails.
(I'll fix the tests after the strings are reviewed since it's just sync'ing the new strings)
Fixes #8966
Testing
Generated and reviewed all emails using
uv run dump-emails.Backend checklist
developif necessary for linear migration historyFor maintainers