Caching 2024 #3615
Labels
2024 chapter
Tracking issue for a 2024 chapter
help wanted: analysts
This chapter is looking for data analysts
help wanted: coauthors
This chapter is looking for coauthors
help wanted: reviewers
This chapter is looking for reviewers
Caching 2024
If you're interested in contributing to the Caching 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
Expand for more information about each role 👀
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
April 15
Complete program and content committee - 🔑 Organizing committee1. Plan content
May 1
First meeting to outline the chapter contents - 🔑 Content team2. Gather data
June 1
Custom metrics completed - 🔑 AnalystsJune 1
HTTP Archive Crawl - 🔑 HA Team3. Validate results
August 15
Query Metrics & Save Results - 🔑 Analysts4. Draft content
September 15
First Draft of Chapter - 🔑 AuthorsOctober 10
Review & Edit Chapter - 🔑 Reviewers & Editors5. Publication
October 15
Chapter Publication (Markdown & PR) - 🔑 AuthorsNovember 1
Launch of 2024 Web Almanac 🚀 - 🔑 Organizing committee6. Virtual conference
November 20
Virtual Conference - 🔑 Content TeamChapter resources
Refer to these 2024 Caching 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-caching on Slack for team coordination
The text was updated successfully, but these errors were encountered: