PWA 2025

[nrllh]

PWA 2025

If you're interested in contributing to the PWA chapter of the 2025 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. You can find more details about this year’s Call for Contributions here.

💬 Please make sure to join #web-almanac-pwa on Slack for team coordination.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@diekus	@diekus @MichaelSolati	@webmaxru @Schweinepriester @aarongustafson	-	@aarongustafson	@Yash-Vekaria

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

• [x] 📆 May 18 Complete program and content committee - 🔑 Organizing committee
  • The content team has at least one author, reviewer, and analyst.

1. Plan content

• [x] 📆 June 1 First meeting to outline the chapter contents - 🔑 Content team
  • The content team has completed the chapter outline.

2. Gather data

• [x] 📆 July 1 Custom metrics completed - 🔑 Analysts
  • Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress.
• [x] 📆 July 1 HTTP Archive Crawl - 🔑 HA Team
  • HTTP Archive runs the June crawl.

3. Validate results

• [x] 📆 September 1 Query Metrics & Save Results - 🔑 Analysts
  • Analysts have queried all metrics and saved the output.

4. Draft content

• [ ] 📆 October 1 First Draft of Chapter - 🔑 Authors
  • Authors has written the chapter.
• [ ] 📆 October 20 Review & Edit Chapter - 🔑 Reviewers & Editors
  • Reviewers and Editors has processed the the chapter.

5. Publication

• [ ] 📆 November 15 Chapter Publication (Markdown & PR) - 🔑 Authors
  • Authors has converted the chapter to markdown and drafted a PR.
• [ ] 📆 December 1 Launch of 2025 Web Almanac 🚀 - 🔑 Organizing committee

6. Live Stream

• [ ] 📆 December 15 Live Stream - 🔑 Content Team

Chapter resources

Refer to these 2025 pwa resources throughout the content creation process:

• 📄 Planning doc for outlining and drafting content
• 📊 Results sheet for saving the results of queries
• 📝 Markdown file for publishing content and managing public metadata
• 🔍 SQL files for committing the queries used during analysis
• 💬 #web-almanac-pwa on Slack for team coordination

[webmaxru]

Hello! Happy to support this initiative again! Please, add me as a reviewer for this chapter.

[Schweinepriester]

heyho! would also be happy to return as a reviewer once more o/

[diekus]

I'm 2 years more experienced in the area since last time I wrote, I'd be happy to author (or co-author, would love some cross vendor team-up) the PWA chapter.

[Yash-Vekaria]

@Suzzicks @aarongustafson @tropicadri @beth-panx @siwinlo @demianrenzulli @thepassle @hemanth @andreban @jeffposnick @MichaelSolati I see that you have contributed to the PWA chapter in previous years. Just wanted to bring this call for contributions for 2025 to your notice in can you would like to contribute to this year's PWA chapter.

[aarongustafson]

I don’t have time to author, but could edit/review

[MichaelSolati]

Last year I dropped the ball and couldn't really organize/contribute. I don't mind helping out @diekus in writing, but I could not take lead.

[nrllh]

@diekus could you take the lead role for this year?

[diekus]

@nrllh I'm in.

[nrllh]

@diekus, could you please try to schedule a meeting with the content team to draft this year's outline? We currently miss an analyst, if we cannot find any analyst, we will need to reproduce the previous analysis which is doable.

[Yash-Vekaria]

@diekus We do not have the chapter outline yet, could you please schedule a meeting with the team to outline it ASAP? Please let us know if we can help in any way. Thank you.

[diekus]

OMG completely lost track of this! @nrllh @Yash-Vekaria when you mention content team, is it the whole group of folks in the chapter? or the authors? or authors and reviewers?

I have join the slack channel, @MichaelSolati let's sync up there?

[Yash-Vekaria]

roup of folks in the chapter? or the authors? or authors and reviewers?

@diekus It's usually the whole team to discuss and finalize the outline and also to then evaluate if any custom metrics need to be implemented for this year's chapter.

[diekus]

@aarongustafson @webmaxru @Schweinepriester @MichaelSolati let's all join the Slack and we can schedule a meeting for next week.

[Schweinepriester]

(sorry, I'm afk on vacation, back on the 14th - but surely you can meet without me)

[MichaelSolati]

Just joined. cyall there

[Yash-Vekaria]

@diekus Just checking to see if you have the outline finalized and custom metrics implemented (if any) for this chapter? If so, please add it to the doc. We are already past the deadline, and this is missing in the docs.