The different facets of the Write the Docs community are kept running smoothly by a wonderful team of folks. We are always looking for more people to help organize conferences and meetups, help out with websites and guides, or take leadership roles in the community. This page documents the roles that people are currently in charge.

If you’re interested in helping out, get in touch with someone on the team you’re curious about. Messaging folks on the Write the Docs Slack is probably the best way to get in touch with folks.


The folks with an asterisk (*) next to their names are the team leads. They get to choose who is in each team, so they are the best folks to talk to about how to join their team.

Conference Teams

Each conference has a specific team that helps run that event. For this year, you can see who is helping out:

Moderation Team

This team helps keep our Slack network on topic and friendly. As a reminder, we expect exemplary behavior from our community, and won’t tolerate any kind of harassment or prolonged negativity.


  • Moderate the Slack network
  • Serve as points of contact for any issues or questions
  • Handle Code of Conduct incidents on Slack or escalate them to the Core Team


Meetup Coordination Team

These are the folks you can talk to about anything Meetups related.

  • Want to attend your first meetup?
  • Start your own meetup?
  • Have any other questions or concerns?


  • Serve as point of contact for people interested in Meetups
  • Update website with new meetups
  • Socialize information around meetups (new meetup topics, speaker ideas)
  • Maintain documentation on starting meetups

Newsletter Team

These folks are in charge of putting out our monthly documentation newsletter to the wider Write the Docs community. The stories in each issue are distilled from conversations that happen across the WTD Slack, which are curated and written by a team of volunteers.


  • Curate Slack conversations and distill them into brief newsletter stories
  • Write a monthly update on general goings-on in the community
  • Round up any Write the Docs events or meetups for the upcoming month
  • Assemble and publish the monthly newsletter to the mailing list and the website

Support Team

Friendly folk on the other end of the email addresses who answer miscellaneous questions about all and sundry. Anything from requests for information, to billing and technical issues.


  • Respond to emails from the community
  • Help folks with anything they need :)


Guide Coordination Team

These are the folks who maintain and make sure it stays high quality. The site is built with Sphinx and hosted on Read the Docs, but we accept content in any format you can send.


  • Serve as point of contact for issues or questions about contributing to the Documentation Guide
  • Update overview and TOC for ease of use
  • Curate and write new sections and topics
  • Identify new contributors and help them get started (like you!)

Social Media Team


  • Manage the @writethedocs twitter account
  • Reply to folks who have questions on Twitter
  • Track, post, and retweet relevant content (2-3 times a day, max)


  • You?

Website Team

These are the folks who maintain and keep it up to date. The site is built with Sphinx and hosted on Read the Docs, so familiarity with these tools is a plus. It’s also a great way to learn them, if you want!


Core Team

Think about the core team like you would the board of a non-profit. They are the folks who are the current leadership of the organization, who create new teams, and are generally responsible for the community.

Generally these folks have done one or more of the following:

  • Chaired a major Write the Docs conference
  • Done more than a year of volunteering to help make Write the Docs a lovely place to be


  • Handle Code of Conduct incidents anywhere
  • Create and dissolve teams
  • Set the general direction for the community and long term goals and business models

Write the Docs Alumni

These are folks who have helped a lot in the past, but have moved on to other projects. We wouldn’t be where we are without them, and want to make sure they aren’t forgotten.


Eric Holscher

Eric is one of the cofounders of Write the Docs, and also one of the cofounders of the Read the Docs documentation platform. He is the primary chair of the Portland conference, and loves to talk all things docs :)

Mikey Ariel

Mikey is the documentation czar for Write the Docs in Europe. She is an avid dancer as well as singer, and has probably traveled across more of Europe than you have. Mikey is a senior technical writer at Red Hat living in Prague.

Samuel Wright

Sam has been organizing Write the Docs conferences for more than a few years now. He lives in Berlin unless he’s off to a conference or death metal festival somewhere. Sam works at Buildkite, and is into using CI/CD to make better docs on CI/CD.

Kelly O’Brien

Kelly runs the Write the Docs newsletter, and has been organizing the North America conference for the last 3 years. She has a day job at Kayako where she is the Self-Service Content Manager.