-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Email content / designs #53
Comments
This is under:
|
Hi, @desigonz & @mailbackwards – This is the last item I'm looking for input on to sum up the 1.5 items. Can you share any content & delivery specs you have? Thanks! |
Hi—my apologies on the delay on this! Liam and I have drafted email templates in this Google doc: https://docs.google.com/document/d/1JRN2bHYVaSMc7kOUc1eoT0fStfhLPSjk76EAKK4KfJk/edit?usp=sharing The first page includes some questions and concerns, which I am pasting in here as well:
|
Thanks, @desigonz! I'll take a look at the content considerations. We do code responsive emails where media queries are supported. I highly suspect that we'd be limited to linking to the app in the browser. I don't think the homescreen app is an addressable app. I added a note in #54 about this, too. Regarding the ESP (Email Service Provider), what are your thoughts? You probably already have an account somewhere that you're using for the DH newsletter. My preference is Campaign Monitor. They have a great segmentation & personalization language and platform, I'm a big fan of their UI, and I'm most well-versed in their template syntax. They also have an excellent API for app integration. Essentially the way I see this playing out is:
Mark |
Hi Mark—just quickly to address the ESP, we use Mailchimp, although that doesn't mean we're wedded to it for Artbot. Do you have any concerns/reservations about working with Mailchimp? |
Now that I've clicked over to the sample content, and to address your follow-up question :) What you've outlined are all automated emails from the app rather than manual sends. In that case, we can make up our own personalization syntax in our own templates and you can handle the blast through any delivery network. Amazon has one, I like Mandrill as an SMTP. Mandrill offers a pretty decent volume of free emails each month. Mandrill is also a MailChimp product. I don't want to make any assumptions about your experience in this realm, but I cannot recommend enough relying on an ESP as an SMTP provider rather than your own server. An ESP is doing their job to keep the network clean and stay in the good graces of ISPs. You should be able to go far with Mandrill for free. Running SMTP on your own server can get it blacklisted. I can now proceed with an assumption that you'll be packaging up the emails in your app's code to deliver via an SMTP provider like Mandrill. I can work in PHP to get the multipart elements (HTML + plaintext) working and mail-able and come up with a "find & replace" syntax for dynamic elements for you. I'll hand those templates back to you and you can integrate them into your app to swap dynamic content in where I have those placeholder tags. Let me know how that sounds? Thanks! /cc @mailbackwards |
Hi Mark, Hope the holidays were great! I'm logging the feedback on the new email designs here to keep the feedback on Github. The designs look great, thanks for getting these to us. Here are my initial thoughts:
Liam, let me know if I missed anything. |
Hi, @desigonz! I'm on board with all of these requests/suggestions. When I run tests, I'll do a Gmail test and view it on my 11" MBA. If we need to constrain the width further, we can do so, though 600px is pretty standard. If you've got 1280 pixels of width, that leaves more than half for the folders on the left and ads on the right. Mark |
Let me know how these edits look? http://email.artx.clearbold.com.s3-website-us-east-1.amazonaws.com Thanks! Mark |
Hi Mark, Thanks for the edits. Just a few thoughts:
Otherwise, it looks good, and thank you for your note on the 600px breakpoint. When you do a Gmail test on your computer, would it be possible to send the same email test to the HyperStudio team? Also, do you have any designs you can send our way so that Liam can get started integrating into the app? |
Hi, @desigonz! How about this to distinguish the sections? http://email.artx.clearbold.com.s3-website-us-east-1.amazonaws.com I'm going to start testing. I'll release code after that, otherwise there will be a lot of shifts in the files you're working with. Mark |
Hi, @desigonz! Here's the full suite of tests. At the time of posting this, the Gmail App for Android test is still running, as are some of the webmail clients, so I haven't cleared those yet. However, Gmail's App is pretty broken, and we hope that most of our Gmail mobile users are doing so through the native iOS or Android Mail app. It's an ongoing issue in the email services industry. Let me know how these look to you: https://litmus.com/pub/2ab5ef3 Mark |
PS Email files & notes can be found in: https://github.com/clearbold/artx/blob/master/email/notes.md Note that I have some tweaks left to do, and still need to do the reminder layout. Mark |
…lar to AOL issue), per Issue #53.
Hi Mark—thanks for this most recent version. We'd prefer not to go with the light gray box to distinguish the sections. Instead, could you make the section titles a bit bigger, and the exhibition titles slightly smaller? Perhaps 20px and 17px, respectively. |
Hi, @desigonz! Those are easy tweaks and I have no concerns optimizing the design for the email context. I did base all of those styles directly on the app so that there would be a seamless transition from email to the app. I.e., the linked events match the formatting of linked events in the app, The headers match the top heading in the app. You can see that here: https://www.dropbox.com/s/i3v96gvlitt6etk/artbot-email-font-sizes.png Want to just confirm those changes before I proceed after taking a look at that? Thanks! Mark |
Hi Mark—having consistent styles between the app and email makes sense, but I think changing the text sizes will make the email more legible. Please go ahead with changing the sizes. Thanks! |
Let me know how these look and I can move forward on the reminder email. These are in the GitHub repository, too. http://email.artx.clearbold.com.s3-website-us-east-1.amazonaws.com/ Thanks! Mark |
Looks great! Thanks a million. |
Hi, @desigonz! Here's a starting point for discussion on the event reminder email. I think the subject and preheader play a key role in this. The event in the email is really just something to click on. That, to me, leaves room to also remind the user of other events in their Favorites. http://email.artx.clearbold.com.s3-website-us-east-1.amazonaws.com/reminder.html Let me know what you think. Thanks! Mark |
Hi Mark, Thanks for this layout, it looks great! A few notes:
Thank you, and have a fantastic weekend! |
Hi, @desigonz!
I've got one in place now.
You'll be able to generate that in your Rails code, swapping "event" and "exhibition" and controlling how many you display. I killed "exhibition" for now.
I have an email service provider "tag" wrapped around that for now so it doesn't yell at me when I use it for testing. (It requires its own unsubscribe link.) That will be in place when I hand these off. Let me know how the teaser looks and I can test & prep this for delivery. http://email.artx.clearbold.com.s3-website-us-east-1.amazonaws.com/reminder.html (Note the server that powers the placeholder images is down at the moment for me. I'm not sure if that will affect you when you take a look.) Thanks! Mark |
Hi Mark—this all looks great. Thanks! |
Hi, @desigonz & @mailbackwards! The final email templates are in our GitHub repository for you. A few notes:
Mark |
Hi Mark-- thanks for these! I'm starting to fold them in now. For now I'm just wondering if the weekly_inline version looks as you would expect... it seems to have much less markup than reminder_inline, and doesn't look different from the source file to me. So I'm wondering if there was a snafu when rendering the inline. The reminder email looks as I would expect though. |
Hi, @mailbackwards! I just pushed an update that should correct those. Mark |
Hi, @desigonz!
I'm opening this issue as a to-do request for sample content for the branded email layouts.
How will you be sending the emails? Is there an ESP I should target? Or will these originate from your app code? Are there placeholder tags that you'll be using?
Thanks!
Mark
/cc @mailbackwards
The text was updated successfully, but these errors were encountered: