-
-
Notifications
You must be signed in to change notification settings - Fork 170
Content Team Leads' Guide
Content team leads are responsible for managing the day-to-day operations for their chapter and coordinating with the rest of the contributors on the content team.
Content team leads are the primary authors for their respective chapters. As the content team lead, you have the authority to decide on the scope and direction for the chapter as well as staffing. For chapters with a broad scope, you may decide to add additional authors or reviewers. You will periodically sync with your Section Coordinator to give status updates and resolve any content/staffing issues that may come up during the project.
The estimated time commitment is approximately 15 additional hours of work over 6 months.
During the initial content planning milestone, the content team leads will:
- work with other authors and reviewers to create the outline of the chapter, which establishes the topics to write about and the metrics needed to support them
- identify staffing gaps depending on the scope/complexity of the chapter and assign new contributors to fill roles accordingly
- maintain the chapter's tracking issue on GitHub to reflect the current contributors, progress on milestones, and any applicable labels
Content team leads ensure that analysts are making good progress on their queries and clarify what the expected results should look like.
When the analysis is complete, the content team will review the results to make sure they're accurate/expected and the content team lead will decide if any revisions are need or whether to begin the writing.
Content team leads assign authors to specific sections of the outline to divide and conquer the chapter. The leads coordinate with authors, reviewers, and analysts to ensure the content and visual figures are accurate and reflective of the data. As the draft comes together, leads coordinate with editors to make sure that the content fits the Web Almanac style guide. When the draft is finalized, leads ensure that the content is submitted in markdown format along with all necessary metadata via GitHub pull request.