nrllh commented 2 months ago

CMS 2024

CMS illustration

If you're interested in contributing to the CMS chapter of the 2024 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 might be interested in exploring the changes to this year's version here.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@sirjonathan	@sirjonathan, @LoraRaykova, @niko-kaleev	@raewrites, @karmatosed	@sirjonathan	-	@turban1988

Expand for more information about each role 👀

- The **[content team lead](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Content-Team-Leads'-Guide)** is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress. - **[Authors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide)** are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases. - **[Analysts](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Section-Leads'-Guide)** 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](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle) doc.

Milestone checklist

0. Form the content team

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

1. Plan content

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

2. Gather data

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

3. Validate results

[ ] 📆 August 15 Query Metrics & Save Results - 🔑 Analysts
- Analysts have queried all metrics and saved the output.

4. Draft content

[ ] 📆 September 15 First Draft of Chapter - 🔑 Authors
- Authors has written the chapter.
[ ] 📆 October 10 Review & Edit Chapter - 🔑 Reviewers & Editors
- Reviewers and Editors has processed the the chapter.

5. Publication

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

6. Virtual conference

[ ] 📆 November 20 Virtual Conference - 🔑 Content Team

Chapter resources

Refer to these 2024 CMS 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 💻 Collab notebook for collaborative coding in Python - if needed 💬 #web-almanac-cms on Slack for team coordination

sirjonathan commented 2 months ago

I'm happy that the project is back again! I'd love to return and contribute as either author or co-author of this year's chapter.

nrllh commented 1 month ago

Hey @alexdenning @dknauss @alonkochba @honzasladek @csliva @dknauss - awesome contributors from previous years 🙂 Are you interested in joining us again this year?

raewrites commented 1 month ago

I'm interested in reviewing. I'm an experienced writer and editor and have previously worked with @sirjonathan. I'll be away most of September but will be back on the 27th, so it would be good to co-review with someone else.

karmatosed commented 4 weeks ago

I am also interested in reviewing. I have experience within the area and can be a subject matter reviewer along with having worked with @sirjonathan to aid collaboration.

turban1988 commented 3 weeks ago

Hi @sirjonathan, Thank you very much for volunteering to lead the writing of this chapter! Could you please organize a kick-off meeting for this chapter (example: https://github.com/HTTPArchive/almanac.httparchive.org/issues/3603#issuecomment-2064351177) to organize the writing of the chapter?

Furthermore, it would be helpful if you and all other contributors (@LoraRaykova, @niko-kaleev, @raewrites @karmatosed ) could join the slack channel of the HTTPArchive (https://join.slack.com/t/httparchive/shared_invite/zt-2hfkn28ts-~uXN4UGS0mXsKpzzhtZcow)

Thanks!

sirjonathan commented 2 weeks ago

@turban1988 I've reached out to the team and am planning to hold the kickoff meeting next week.

sirjonathan commented 2 days ago

@LoraRaykova, @niko-kaleev, and I met today. We discussed the previous years efforts and ideas for improving / expanding this year's chapter, including references to the Speculation Rules API and tracking themes within the WordPress section.

Our plan is to start by pulling over the 2022 outline and expand it with our ideas for this year. @niko-kaleev will take the first pass at that and we'll work on it together async.

We're meeting again on the 28th to finalize the outline after which I'll follow-up on any analyst related tasks.

/cc @turban1988

niko-kaleev commented 1 day ago

As discussed with @sirjonathan and @LoraRaykova on the kick-off meeting, the chapter outline is ready:

https://docs.google.com/document/d/13CxAp7HCcxHHCSuEnXS2rolKskLSlUvLQuqUD6QADYc/edit

@sirjonathan will review it next week, and we'll finalize it on the 28th.