Commit d51909e5 authored by Erica 's avatar Erica

Merge branch 'update-blog-hb' into 'master'

Add scheduling info to hb

See merge request !15758
parents e1a538e1 f19e1c29
Pipeline #34044838 passed with stages
in 27 minutes and 16 seconds
......@@ -103,6 +103,15 @@ Reviewer – check these before you publish:
When you have double checked, you can assign to @rebecca to merge. If Rebecca is OOO, assign to @erica.
### Publishing schedule
With the exception of time-sensitive announcements and news, we are aiming to have blog posts scheduled two weeks ahead.
- We will publish 3-5 posts per week, avoiding publishing more than once in day.
- We will stagger publishing, generally avoiding posting on Fridays and in the last few days of the month.
- We don't consider operational posts (patch release announcements, for example) as conflicting with other publishing, so we may publish a post on the same day that one of those goes live.
- We aim to ensure that posts that are likely to be popular are live in time to be included in the bi-weekly newsletter that goes out on the 10th and 25th of each month.
## Publishing natively on LinkedIn and Medium
Occasionally, some blog posts are better suited to publishing natively by the author on LinkedIn, or on [Medium]( We reach slightly different audiences on these channels, and some content will get better exposure and reach if published there. If you submit a blog post and the content team decides it's a better fit for one of these, we will let you know. For now, we will treat this segmentation as an experiment, monitor the performance of different types of content on different channels, and apply our learnings. We may then be able to start planning content for specific outlets and commission stories accordingly.
......@@ -284,7 +293,7 @@ You can include as many tags as you like, separated by commas. Please only inclu
- careers
- CI
- cloud native
- code reivew
- code review
- collaboration
- community
- demo
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment