Inconsistent casing of subject lines in emails #1684
Comments
|
cc @ryanfeeley |
|
@philbooth Is there an easy way to extract all the email subject lines and post them here? I'll have the content team make the call on all of them. |
|
@ryanfeeley, here you go old bean: |
|
So appreciated! |
|
When we look at a screenshot of our current emails, it's apparent that mentioning Firefox Accounts is somewhat redundant. We can improve our emails significantly by simply trimming them down (and including codes in subject line where possible). I also ran them all through a title case tool. Here is where I landed. Any concerns? I'll check with Jeff as well.
|
|
Subjects are being updated here: https://docs.google.com/document/d/1LRf1SiFg3zxJbDVFbilCUVDKjKcRt4_cnT_epzKm684/edit?usp=sharing |
|
Hey @ryanfeeley, I just started to make these changes and I realised there were some subjects I missed when I listed them before. Sorry, there's conditional code and not all the subjects get generated by the test I ran. These are the ones I missed: (alternative subjects for the And: (alternative subject for the |
|
WIP PR is at #2017. I'll get that reviewed as soon as decisions/strings are final here. |
|
New guidance - re-sentence case the titles - info here: https://docs.google.com/document/d/1LRf1SiFg3zxJbDVFbilCUVDKjKcRt4_cnT_epzKm684/edit |
|
Update per: @shane-tomlinson We would keep the strings as is in code, so no change for the l10n team. https://docs.google.com/document/d/1LRf1SiFg3zxJbDVFbilCUVDKjKcRt4_cnT_epzKm684/edit?usp=sharing |
|
@ryanfeeley Do we want to do anything else in this issue or should we close it? |
|
@clouserw Is it done? |

Most of the FxA emails have the subject line in sentence-casing. But while reviewing #1675, I noticed that "Finish Creating Your Account", "Reminder: Finish Creating Your Account" and "Your Firefox Account is Confirmed" have title-casing.
It looks like it's how they were specified in the designs for #1073 / #1087, but that seems weirdly inconsistent to me. Is it a bug or a feature?
The text was updated successfully, but these errors were encountered: