Page Weight 2022

[rviscomi]

Page Weight 2022

If you're interested in contributing to the Page Weight chapter of the 2022 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@fellowhuman1101	@fellowhuman1101 @dwsmart	@CSteele-gh @mordy-oberstein	@drohe	-	@paulcalvano

Expand for more information about each role 👀

• The content team lead is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress.
• Authors are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report.
• Reviewers are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases.
• Analysts are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly.
• Editors are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit.
• The section coordinator is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule.

Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors.

For an overview of how the roles work together at each phase of the project, see the Chapter Lifecycle doc.

Milestone checklist

0. Form the content team

• May 1: The content team has at least one author, reviewer, and analyst

1. Plan content

• May 15 The content team has completed the chapter outline in the draft doc

2. Gather data

• June 1: Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress

• June 1 - 15: HTTP Archive runs the June crawl

3. Validate results

• August 1: Analysts have queried all metrics and saved the output to the results sheet

4. Draft content

• September 1: The content team has written, reviewed, and edited the chapter in the doc

5. Publication

• September 15: The completed chapter and all required metadata and figures are converted to markdown and submitted to GitHub

• September 26: Target launch date 🚀

Chapter resources

Refer to these 2022 Page Weight resources throughout the content creation process:

📄 Google Docs for outlining and drafting content
🔍 SQL files for committing the queries used during analysis
📊 Google Sheets for saving the results of queries
📝 Markdown file for publishing content and managing public metadata
💬 #web-almanac-page-weight on Slack for team coordination

[fellowhuman1101]

@dwsmart and I volunteer to author 🤘

[dwsmart]

Happy to help author on this one.

[rviscomi]

@fellowhuman1101 would you be able to take on the content team lead role? You'd be responsible for project-managing this chapter and keeping it on track.

[rviscomi]

@fellowhuman1101 @dwsmart also could you both request access to the chapter planning doc and start outlining the contents of the chapter? We also have a #web-almanac-page-weight channel on Slack where you and the rest of the team can coordinate.

For now the most pressing task is to staff the rest of the content team with at least one reviewer and analyst (technically due yesterday). Could you reach out to your networks to see if anyone would be interested to join? Alternatively, one of you could be the reviewer and/or analyst.

After that, the next milestone is to complete the outline by May 15.

[fellowhuman1101]

@rviscomi happy to take on project management for this chapter. Access to the planning doc requested.

[rviscomi]

Thanks @fellowhuman1101! Access granted 🟢 🟢 🟢

[drohe]

Hi! I'd be happy to take on the analyst role!

[CSteele-gh]

I'd like to be a reviewer

[rviscomi]

Great, thank you and welcome @CSteele-gh! See #2899 (comment) for the next steps.

@fellowhuman1101 now that the content team is filled out with at least one person in each role, you can check off Milestone 0 at the top of the issue. At this stage everyone should be collaborating on the outline in the chapter doc with the goal of having it completed by May 15.

[mordy-oberstein]

Would be happy to help

[rviscomi]

Thanks @mordy-oberstein! I presume you're interested in the Reviewer role?

[rviscomi]

@fellowhuman1101 @dwsmart @CSteele-gh @mordy-oberstein @drohe hi all, reminder to access the planning doc and start brainstorming content for the outline. We're hoping to have that completed by May 15 to stay on schedule. Thanks!

[rviscomi]

@fellowhuman1101 @dwsmart @CSteele-gh @mordy-oberstein the analysis is done and the results are available in the sheet. Go through the results and ping @drohe if you have any questions.

@fellowhuman1101 please coordinate with your team to get the draft written, reviewed, and edited by September 1 to ensure that it's released on time. You may want to divide up the sections with @dwsmart to write in parallel. You should also give your reviewers an expectation of when the draft will be ready for review so they can carve out the time. There isn't currently an editor assigned so reach out to @paulcalvano when the draft is reviewed and we'll find one for you.

Looking forward to reading it! 🚀

[fellowhuman1101]

@paulcalvano we're ready for an editor