-
Notifications
You must be signed in to change notification settings - Fork 483
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
Launching the first HogMail newsletter #3156
Comments
Reasoning for these? The header bar is designed to give it more of a webpage feel, and the dashed lines match our dashed line in our branding elsewhere. (The solid We also have a font we've been using in emails (Poppins) that seems to have gone missing here! And maybe we can center-align the title while we're at it? |
RE: header links and table borders:
RE the font and other bits:
|
Lottie's artwork, which is fabulous. |
Okay, I see. (I was missing this context.) I'm going to try to revisit this next week to see if we can come up with a more personal feel that still fits within our style. |
Only feedback from me on latest version would be moving the PostHog News bit at least above the Stuff We're Reading section. Stuff We're Reading feels like a nice misc. close, while PostHog News seems more important to drive attention to. No strong feelings though. |
Yeah, makes sense. I'll do a switcherooo. |
We're at a point where we're nearly ready to launch our new newsletter, HogMail. There's a just a few oustanding items.
Target Launch Date: Friday, March 25
Draft Template: On Mailchimp (account needed to access)
To Do:
Desired changes to the template
In the intro section, Lottie is designing an avatar we'd like to have right-aligned with the copy flowed around it
I'd like to remove the header links at the top (Learn more about PostHog) etc. for this email
Likewise, I'd prefer not to have the dashed table borders. My preference is this should look as much as possible like a normal email, but this isn't dealbreaker particularly
The text was updated successfully, but these errors were encountered: