Here are some guidelines for writing the Developer Relations Newsletter, but first be sure to read and respect our Markdown guideline when writing the newsletter.
- First week: content propositions
- Second week: write blog post (if needed)
- Third week: draft the newsletter and send test
- Fourth week: send the newsletter
It is recommended by Mailchimp to use no more than 9 words and 60 characters since multiple people will read your email on a mobile device.
Capitalize the first word except for conjunctions and try to keep the headers short.
Gmail clips emails that have a message size larger than 102KB (source: Mailchimp), so we need to limit the content to what is the most important. We should also adapt our content in a excerpt pointing on our blog, video on YouTube or to our documentation for more information. Here is a guided format for the newsletter content
- Subject heading
- Introduction
- Highlight information(if any)
- Product updates(arranged based on products)
- Other fun stuff(if any)
- Videos/Presentations(if any)
- Latest articles
- Article in developers world
The newsletter content should be properly spaced. Add a spacer at the end of a paragraph.
Buttons may be included in the newsletter, however it should be limited to the main CTA. When using button you need to adhere to the standard button design, which has a border radius of 4px and the color #FD3426.
The newsletter should be sent to the [devrel] Newsletter contact list only.