Difference between revisions of "XMPP Newsletter"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
=== Process === | === Process === | ||
# | # Link collection: duration 1 month | ||
#* Read and validate the content | |||
#* Include the reporters credits! | |||
# Copywrite so each content is readable by humans: duration 1 week | |||
#* Add links | |||
#* Add images | |||
#* Add CTAs | |||
#* Carefully craft the subject/title line, and the preview text (first lines that are sometimes previewed on email UAs) | |||
#* Include the copywriters credits! | |||
# PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting | |||
#* Include Pelican header | |||
#* Change == in # | |||
#* Change links format | |||
#* Change images format | |||
#* Need at least 2 or 3 peer reviews | |||
#* Include the reviewers credits! | |||
# Sending the newsletter: on D-day | # Sending the newsletter: on D-day | ||
## Copy-paste Newsletter on Tinyletter | ## Copy-paste Newsletter on Tinyletter | ||
## | ## Test it (peer review is not yet done) | ||
# | ## Send it | ||
# Blog post: PR merge and deploy on website git repo on D-day | |||
# Social media posts | # Social media posts | ||
#* text | |||
#* image | |||
#* hashtags | |||
#* link | |||
# Metrics/analytics in CommTeam MUC | |||
#* Twitter monthly metrics | |||
#* Newsletter analytics | |||
# Propose schedule for next issue | |||
# Translations: after D-day | # Translations: after D-day | ||
Revision as of 20:51, 3 December 2019
Here you can submit news items for inclusion in the next XMPP Newsletter (as managed by the CommTeam).
To contributors, editors, reviewers, translators
Live discussion
xmpp:commteam@muc.xmpp.org?join
What determines relevancy?
The submission must ideally be a blog or article about XMPP/Jabber and/or XMPP-based software (clients, servers, libs).
Some exceptions might be made, for example for a release page showing a new release of some XMPP-based software.
However, marketing brochures (e.g. single-page marketing sites) for new products which don't contain information on XMPP, won't be included.
Make sure you read the Basic communication guide for XMPP techies
Process
- Link collection: duration 1 month
- Read and validate the content
- Include the reporters credits!
- Copywrite so each content is readable by humans: duration 1 week
- Add links
- Add images
- Add CTAs
- Carefully craft the subject/title line, and the preview text (first lines that are sometimes previewed on email UAs)
- Include the copywriters credits!
- PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting
- Include Pelican header
- Change == in #
- Change links format
- Change images format
- Need at least 2 or 3 peer reviews
- Include the reviewers credits!
- Sending the newsletter: on D-day
- Copy-paste Newsletter on Tinyletter
- Test it (peer review is not yet done)
- Send it
- Blog post: PR merge and deploy on website git repo on D-day
- Social media posts
- text
- image
- hashtags
- link
- Metrics/analytics in CommTeam MUC
- Twitter monthly metrics
- Newsletter analytics
- Propose schedule for next issue
- Translations: after D-day
Planning
January:
- 2020-01-30 Mon: copywriting starts
- 2020-01-03 Fri: end of link submission, PR on GitHub
- 2020-01-07 Tue: newsletter publication, blog post, promotion tweets
