Case Study: GitHub Editorial

Overview
‍Creating a global content presence for developers

I was a copywriter turned Editorial Manager / Content Manager for the GitHub Blog, Product Manager and Content Designer for GitHub Sponsors, and served on the Inclusion Advisory Council.

As a Content Manager, I managed the blog pipeline as content was drafted, edited, and published through GitHub or WordPress.‍‍

Check out the GitHub blog archives from 2018 - 2019 (I’ve ghost-written or edited almost every post).
I debuted as an author when I transitioned from Content Manager to Product Manager.
I wrote content and supported launches through the Microsoft acquisition, GitHub India, Octoverses, GitHub Sponsors expansion to countries like Malta and Cyprus, and more.
Through my time at GitHub, I've overhauled and created guidelines and templates for internal and external processes, audiences, and partners.

Goals
Create processes to enable contribution

📝
Help developers contribute content
It's great to have content options, but a backlog of content just means that by the time an editor gets to the material, it may already be stale. This frustrates the author and can result in project delays.

The content team needed a way to review drafts and share feedback timely, with a way to prioritize and schedule different requests.
🌱
Make processes that scale
During my time at GitHub, we were acquired by Microsoft. Because of the acquisition, we increased in numbers and needed content processes that can adapt to a larger volume of requests and editors.
💡
Educate and delight audiences
While we were growing after the Microsoft acquisition, we wanted content to still have the same approachable, educational, and supportive voice and tone our community knows and loves.

Challenges
Growing pains

⏱️
Many challenging timelines across priorities
<still working on this page>
🎛️
Evolving needs through acquisition
<still working on this page>
🔮
Many collaborators and tools
<still working on this page>