CMS 2025
CMS 2025

If you're interested in contributing to the CMS 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-cms on Slack for team coordination.
Content team
| Lead | Authors | Reviewers | Analysts | Editors | Coordinator |
|---|---|---|---|---|---|
| @VaheSODP | @VaheSODP @blogsmithteam | @dknauss @raewrites @alonkochba | - | @dknauss @CBID2 | @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 18Complete program and content committee - π Organizing committee- The content team has at least one author, reviewer, and analyst.
1. Plan content
- [x] π
June 1First meeting to outline the chapter contents - π Content team- The content team has completed the chapter outline.
2. Gather data
- [x] π
July 1Custom metrics completed - π Analysts- Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress.
- [x] π
July 1HTTP Archive Crawl - π HA Team- HTTP Archive runs the June crawl.
3. Validate results
- [x] π
September 1Query Metrics & Save Results - π Analysts- Analysts have queried all metrics and saved the output.
4. Draft content
- [ ] π
October 1First Draft of Chapter - π Authors- Authors has written the chapter.
- [ ] π
October 20Review & Edit Chapter - π Reviewers & Editors- Reviewers and Editors has processed the the chapter.
5. Publication
- [ ] π
November 15Chapter Publication (Markdown & PR) - π Authors- Authors has converted the chapter to markdown and drafted a PR.
- [ ] π
December 1Launch of 2025 Web Almanac π - π Organizing committee
6. Live Stream
- [ ] π
December 15Live Stream - π Content Team
Chapter resources
Refer to these 2025 cms 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-cms on Slack for team coordination
Iβd love to be an editor on this
@sirjonathan, @csliva, @alexdenning, @dknauss, @alonkochba, @honzasladek, @niko-kaleev, @LoraRaykova, @raewrites, @karmatosed I see that you have contributed to the CMS chapter in 2022 or 2024. Just wanted to bring this call for contributions for 2025 to your notice in can you would like to contribute to this year's CMS chapter.
@Yash-Vekaria I'm happy to be a reviewer again this year. @dknauss β wanna join me?
Sure, I will be a review and/or editor again @Yash-Vekaria.
Hi! I can also review this year's chapter.
I'd be interested in being an author for this chapter given our exposure to different platforms on SODP
Interested in being an author!
@VaheSODP, could you please try to schedule a meeting with the content team to draft this year's outline?
Hi @dknauss, @blogsmithteam, @raewrites, @alonkochba, and @CBID2, not everyone is on Slack yet. To help me coordinate a day this upcoming week, please provide your time zone and email address via a Slack DM to protect your privacy. I am looking to schedule a time this week, Wednesday or Thursday.
Look forward to working with everyone :)
@VaheSODP we still miss the outline, could you please draft the outline with your team ASAP? Thank you!
@VaheSODP 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.
guys the outline was shared on slack over a few weeks ago - https://docs.google.com/document/d/1Y1tMPMk-G9qfk8nZomLPDG14kVjj7UV3M13_SPcXfwo/edit?usp=sharing
There are no analysts for the project and we need extra support for this to get this going quicker. any support would be appreciated. blogsmithteam has also pulled out as a supporting author so plz advise what to do
@VaheSODP In the worst case, if no one else from the team wants to volunteer in an analyst role, we can simply reproduce the results from the previous edition. @nrllh reproduced SQLs for cms chapter last year and can help this year too, however he cannot extend the analysis. So, if the team is not planning to extend the analysis, we should be fine.