Difference between revisions of "XMPP Newsletter"

From XMPP WIKI
Jump to: navigation, search
(Planning)
(Past newsletters)
 
(13 intermediate revisions by 2 users not shown)
Line 26: Line 26:
 
#* Read and validate the content
 
#* Read and validate the content
 
#* Include the reporters credits!
 
#* Include the reporters credits!
 +
#* Check that it's not duplicate, and in the correct section
 
# Copywrite so each content is readable by humans: duration 1 week
 
# Copywrite so each content is readable by humans: duration 1 week
 
#* Add links
 
#* Add links
Line 33: Line 34:
 
#* Include the copywriters credits!
 
#* Include the copywriters credits!
 
# 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: date, time, file name
 
#* Translate Mediawiki syntax to Github's Markdown: https://sinnwerkstatt.github.io/MediaWiki-to-Markdown-Javascript-Converter/
 
#* 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
Line 55: Line 56:
 
=== Planning ===
 
=== Planning ===
  
February:
+
March:
  
* 2020-01-27 Mon: copywriting starts
+
* 2020-02-24 Mon: copywriting starts
* 2020-01-30 Thu: end of link submission, PR on GitHub (during XMPP Summit)
+
* 2020-02-28 Thu: end of link submission, PR on GitHub (during XMPP Summit)
* 2020-02-04 Tue: newsletter publication, blog post, promotion tweets
+
* 2020-03-03 Tue: newsletter publication, blog post, promotion tweets
  
 
=== Current newsletter ===
 
=== Current newsletter ===
Line 65: Line 66:
  
 
* [[XMPP Newsletter template]]
 
* [[XMPP Newsletter template]]
* [[XMPP Newsletter February 2020]] (current)
+
* [[XMPP Newsletter August 2020]] (next)
 +
* [[XMPP Newsletter July 2020]]
  
 
=== Past newsletters ===
 
=== Past newsletters ===
Line 72: Line 74:
 
* [[XMPP Newsletter December 2019]]
 
* [[XMPP Newsletter December 2019]]
 
* [[XMPP Newsletter January 2020]]
 
* [[XMPP Newsletter January 2020]]
 +
* [[XMPP Newsletter February 2020]]
 +
* [[XMPP Newsletter March 2020]]
 +
* [[XMPP Newsletter April 2020]]
 +
* [[XMPP Newsletter May 2020]]
 +
* [[XMPP Newsletter June 2020]]
  
 
=== Translations ===
 
=== Translations ===
Line 82: Line 89:
 
=== Metrics, statistics, analytics===
 
=== Metrics, statistics, analytics===
  
* https://framapic.org/kk22EvOJZldF/qzHYacsAE8sc.png
+
* Newsletter:
* https://framapic.org/hDaDBf7lgqK2/Na0Mb80LO9dn.png
+
** [https://framapic.org/sVngR3A08PpP/8fuywT3kzC5O.png Absolute subs growth]
* https://framapic.org/UBf3oKbYPpQr/KpRkvV3FOqNC.png
+
** [https://framapic.org/vzduKYC5Itaa/om4Vu44zp9F0.png Relative subs growth]
 +
** [https://framapic.org/VHietwQqOHTk/QVWMfe66o21K.png Open and click rates]
 +
* [https://framapic.org/C5DFC82ifPhq/RS9ZPXgW7FDp.png Twitter metrics]

Latest revision as of 19:18, 2 August 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

  1. Link collection: duration 1 month
    • Read and validate the content
    • Include the reporters credits!
    • Check that it's not duplicate, and in the correct section
  2. 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!
  3. PR on website git repo for blog post (Markdown, Pelican): duration the week-end before posting
  4. Sending the newsletter: on D-day
    1. Copy-paste Newsletter on Tinyletter
    2. Test it (peer review is not yet done)
    3. Send it
  5. Blog post: PR merge and deploy on website git repo on D-day
  6. Social media posts
    • text
    • image
    • hashtags
    • link
  7. Metrics/analytics in CommTeam MUC
    • Twitter monthly metrics
    • Newsletter analytics
  8. Propose schedule for next issue
  9. Translations: after D-day

Planning

March:

  • 2020-02-24 Mon: copywriting starts
  • 2020-02-28 Thu: end of link submission, PR on GitHub (during XMPP Summit)
  • 2020-03-03 Tue: newsletter publication, blog post, promotion tweets

Current newsletter

Past newsletters

Translations

Metrics, statistics, analytics