Difference between revisions of "XMPP Newsletter"
Jump to navigation
Jump to search
| (5 intermediate revisions by the same user not shown) | |||
| Line 34: | Line 34: | ||
# PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting | # PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting | ||
#* Include Pelican header | #* Include Pelican header | ||
#* | #* Translate Mediawiki syntax to Github's Markdown: https://sinnwerkstatt.github.io/MediaWiki-to-Markdown-Javascript-Converter/ | ||
#* Need at least 2 or 3 peer reviews | #* Need at least 2 or 3 peer reviews | ||
#* Include the reviewers credits! | #* Include the reviewers credits! | ||
| Line 57: | Line 55: | ||
=== Planning === | === Planning === | ||
February: | |||
* | * 2020-01-27 Mon: copywriting starts | ||
* 2020-01- | * 2020-01-30 Thu: end of link submission, PR on GitHub (during XMPP Summit) | ||
* 2020- | * 2020-02-04 Tue: newsletter publication, blog post, promotion tweets | ||
=== Current newsletter === | === Current newsletter === | ||
* [[XMPP Newsletter template]] | * [[XMPP Newsletter template]] | ||
* [[XMPP Newsletter February 2020]] ( | * [[XMPP Newsletter February 2020]] (current) | ||
=== Past newsletters === | === Past newsletters === | ||
| Line 73: | Line 71: | ||
* [[XMPP Newsletter November 2019]] | * [[XMPP Newsletter November 2019]] | ||
* [[XMPP Newsletter December 2019]] | * [[XMPP Newsletter December 2019]] | ||
* [[XMPP Newsletter January 2020]] | |||
=== Translations === | === Translations === | ||
| Line 83: | Line 82: | ||
=== Metrics, statistics, analytics=== | === Metrics, statistics, analytics=== | ||
https://framapic.org/ | * https://framapic.org/kk22EvOJZldF/qzHYacsAE8sc.png | ||
* https://framapic.org/hDaDBf7lgqK2/Na0Mb80LO9dn.png | |||
* https://framapic.org/UBf3oKbYPpQr/KpRkvV3FOqNC.png | |||
Revision as of 09:24, 15 January 2020
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
- Translate Mediawiki syntax to Github's Markdown: https://sinnwerkstatt.github.io/MediaWiki-to-Markdown-Javascript-Converter/
- 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
February:
- 2020-01-27 Mon: copywriting starts
- 2020-01-30 Thu: end of link submission, PR on GitHub (during XMPP Summit)
- 2020-02-04 Tue: newsletter publication, blog post, promotion tweets
