#6287 closed enhancement (fixed)
Improve the new layout of Make/P2 blogposts email notifications
Reported by: | audrasjb | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Mailing Lists | Keywords: | |
Cc: |
Description
A new layout for Make/WordPress P2's blogposts email notifications was rolled out today, and it is a very nice improvement for the readability of those emails.
However, they could probably benefit from a few tweaks/adjustments:
- Change the sender email address (
<donotreply@wordpress.com>
) to a dotorg domain name - Replace the Jetpack logo at the top of the email with a WP logo (or simply just remove it, as it would be better for the general layout of the email)
- In my opinion, the "Optimized by Jetpack" link at the bottom is fine, but I wouldn't disagree is someone would ask to remove it to make it more "dotorg-friendly" :-)
- Remove the two unappropriate Apps buttons at the bottom (I believe they are pretty useless, but I can be mistaken!)
Attachments (3)
Change History (20)
#2
@
3 years ago
Added an attachment showing the new emails.
I believe this would be the site icon if defined. The make sites appear not to have this set so I think something that we can do on the meta side of the coin.
As shown, The accessibility site has an icon defined, but the Core blog doesn't.
I don't think we had a reason to set this previously, but we do have a filter to alter other Jetpack images, such as the default share image, etc.
In my opinion, the "Optimized by Jetpack" link at the bottom is fine
I say leave it, if for no other reason, there is not a Jetpack feature/option to remove it.
Agreed, it's one of the unfortunate side-effects we have of using Jetpack functionality, we can't alter the emails :)
Worth noting that it looks like it's AB tested, as I get "Powered by Jetpack" which makes more sense.
Remove the two unappropriate Apps buttons at the bottom (I believe they are pretty useless, but I can be mistaken!)
I didn't get an e-mail from make/core (I follow via RSS, not via e-mail). Which app do the links direct to?
It looks like it's the Jetpack App, eg, https://jetpack.com/app?campaign=email_ios_badge
which IIRC is a redirect to the App store if on a supported device, otherwise to the Jetpack info page about the app.
#3
@
3 years ago
Added a screenshot of the previous emails, for reference. Looks like the Logo on those was a fallback blavatar, which happened to be a generic WordPress.com single-ring logo.
Replying to dd32:
Remove the two unappropriate Apps buttons at the bottom (I believe they are pretty useless, but I can be mistaken!)
I didn't get an e-mail from make/core (I follow via RSS, not via e-mail). Which app do the links direct to?
It looks like it's the Jetpack App, eg,
https://jetpack.com/app?campaign=email_ios_badge
which IIRC is a redirect to the App store if on a supported device, otherwise to the Jetpack info page about the app.
FWIW Jetpack-blogs get that, WordPress.com sites get the WordPress App I think.
It would make more sense to me, that Site members would get the Jetpack 'Management app', but subscribers would get the 'WordPress app' to use the reader/etc..
#4
@
3 years ago
The Automattic team handling the email updates is going to move forward with the following:
- Leaving the WordPress.com sender (as that's not something new)
- Using a generic WordPress logo for *.WordPress.org sites without a site icon.
- Removing the Powered by text for w.org sites.
- Updating the app links to WordPress.org/mobile/
I'll leave this ticket open until that's all complete. We can add site icons to sites here in the meantime until they can deploy those changes.
This ticket was mentioned in Slack in #meta by kraft. View the logs.
3 years ago
#7
follow-up:
↓ 9
@
3 years ago
Do we have a complete list of non wordpress.org sites that will need accounting for too? The WordCamp and foundation sites come to mind
Thanks for the fast work on resolving this!
#8
@
3 years ago
Would it also make sense from the .org network side to ensure there are site icons set for the different sites?
#9
in reply to:
↑ 7
@
3 years ago
Replying to TJNowell:
Do we have a complete list of non wordpress.org sites that will need accounting for too? The WordCamp and foundation sites come to mind
I don't know that we do. There hasn't been a consistent way to flag WordPress Project sites. (*.)wordpress.org
, (*.)wordcamp.org
, wordpressfoundation.org
should handle the vast, vast majority of sites under the Project's portfolio that would have Jetpack and Jetpack Subscriptions specifically enabled.
Once we deploy all of this, we'll have a centralized function to put cases to catch, so adding more will be trivial if there are any to add.
#10
@
3 years ago
It would be great if we had multiple layers, set the icons, checks on the jetpack side, but also doing it in code. I'm unsure if we can override the site icon with a URL string or if it requires that we localise an attachment but someone more familiar with Jetpack code would be better suited than me to advise on that.
#11
follow-up:
↓ 13
@
3 years ago
The site icon is Core's functionality (abandoned out of Jetpack once it went into Core), so the various core filters should work (or I'll ensure they do if there are issues, but I'm not aware of any right now).
#13
in reply to:
↑ 11
@
3 years ago
Replying to kraftbj:
the various core filters should work
The above commit has updated the site icon, and the above image shows it works :) It's showing https://i0.wp.com/s.w.org/images/wmark.png?resize=256,256&ssl=1
#14
@
3 years ago
- Keywords close added
- ☑️ Change the sender email address (<donotreply@…>)[wontfix]
- ✅ Replace the Jetpack logo at the top of the email with a WP logo. [Generic WordPress logo used for w.org sites, including WordCamp and WPF, no site icon set --
- ✅ The "Optimized by Jetpack" link at the bottom is fine [Removed]
- ✅ two Apps buttons at the bottom [Using wordpress.org/mobile instead]
The above things have been deployed on the WordPress.com side (internal ref D79200, D79299, D79216). I don't have the privs to mark this as fixed, but I believe it can be resolved as such.
#15
@
3 years ago
- Resolution set to fixed
- Status changed from new to closed
Marking as fixed, thanks!
Replace the Jetpack logo at the top of the email with a WP logo. [Generic WordPress logo used for w.org sites, including WordCamp and WPF, no site icon set --
Noting that *.wordpress.org sets a generic logo that appears to be being respected. Without digging into the a8c side of the changes, it appears to me that this is only set as the default fallback when a site doesn't specify an alternative logo.. which works for us I think.
#16
@
3 years ago
- Keywords close removed
Yes, correct. The a8c-side change for the site icon is a fallback when there is no site icon set on the client site in any way. It's duplicative of the work you did on the w.org side, but rather be safe while we had folks touching that code on the a8c side.
I couldn't recall if the WordCamp network set site icons automatically or not, but the a8c-side change will also ensure any WordCamp sites without a site icon will not use the Jetpack icon either.
Noting that this has been the sender for a long time. The e-mails are sent from the WordPress.com system (via the Jetpack subscriptions feature), so it's accurate in terms of identifying the sending server (Jetpack Subscriptions does not offer a feature to send on behalf of a site).
I believe this would be the site icon if defined. The make sites appear not to have this set so I think something that we can do on the meta side of the coin.
I say leave it, if for no other reason, there is not a Jetpack feature/option to remove it. :-). In all seriousness, open to hearing other thoughts on it and relaying that feedback as well.
I didn't get an e-mail from make/core (I follow via RSS, not via e-mail). Which app do the links direct to? If the WordPress app, the site reader functionality within it could make sense. If it is the Jetpack app, IMO, I'm not sure how it is helpful since that's more for site admins than site visitors. I can pass that feedback to the team at Automattic working on the e-mails.