GatsbyJS Newsletter

[shannonbux]

Description

We have a lot of people signed up through MailChimp to receive a GatsbyJS newsletter, and they haven't received anything yet :) which means we need to actually write newsletters. Suggestions on the following?

Format:

• Product announcements, new features
• Bug fixes
• Site highlight of the week + interview with site's creator
• New docs / tutorials / UX projects that have been finished or need help
• Funny quote
• Recommended reading
• Blogposts

Options for how to create drafts:

• We could create a Trello board and throw links to articles on there and then we'll link to the Trello board in the email
• We could have a shared google drive folder and send out a new googledoc every week
• We could somehow draft things in github (not my preference since imho googledocs work much better for long-form prose editing & reviews)

[alysonpaige]

I saw the first newsletter went out yesterday, nice job! Need any help?

[shannonbux]

Hey @alysonpaige for sure! What kinds of things would you like to help with? And what collaboration environment do you prefer? We're drafting the emails in MailChimp currently. There are some more ideas above in this issue (googledocs, trello, etc.)

[alysonpaige]

@shannonbux Trello or Google Docs is fine, I'm flexible so whatever works for you or the current workflow. If interested, there could be a section on Gatsby in the News or "In the Wild" which could link to external sources of either well polished Gatsby sites or articles or references that make positive mention of Gatsby. I can help with the newsletter format/creation or the aggregation of content available to include in them. If you have any suggestions, let me know - I'm open!

[shannonbux]

That'd be awesome! Email me at [email protected] from whatever email you'd like to use to collaborate and I'll invite you to the next newsletter draft :)

[shannonbux]

Closing this issue for now because @alysonpaige and I will handle May's newsletter. Always happy for more help with this if anyone runs across this closed issue!