almanac.httparchive.org
almanac.httparchive.org copied to clipboard
Cookies 2025
Cookies 2025

If you're interested in contributing to the Cookies 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-cookies on Slack for team coordination.
Content team
| Lead | Authors | Reviewers | Analysts | Editors | Coordinator |
|---|---|---|---|---|---|
| - | @yohhaan @ajackley | @martinakraus @JannisBush | - | @bsmth | @burakguneli |
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 18Complete program and content committee - π Organizing committee- The content team has at least one author, reviewer, and analyst.
1. Plan content
- [ ] π
June 1First meeting to outline the chapter contents - π Content team- The content team has completed the chapter outline.
2. Gather data
- [ ] π
July 1Custom metrics completed - π Analysts- Analysts have added all necessary custom metrics and drafted a PR (example) to track query progress.
- [ ] π
July 1HTTP Archive Crawl - π HA Team- HTTP Archive runs the June crawl.
3. Validate results
- [ ] π
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 cookies 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-cookies on Slack for team coordination
Hi @burakguneli, I am interested in joining as a reviewer for this chapter
@martinakraus that's great, thanks!!
Hello @ydimova @samdutton @yohhaan, thank you so much for your contributions in 2024 π How are you feeling about joining this year too?
Hi @burakguneli,
Thanks for the ping! I am interested in joining as an author for this 2025's edition (and can also help someone else who would be the main analyst on this chapter with a few queries on the side). Thanks!
@martinakraus @yohhaan thank you so much for your interest! We need more people to help us with chapter. Is there any chance you have some colleagues/friends who would like to work with us for this year's chapter?
Will spread the word around it. I have already an idea who might can help, let's see if he has time
@burakguneli I would like to join as a reviewer on this chapter
@JannisBush welcome onboard :)
@burakguneli I would like to join as a reviewer if you still need
@burakguneli I would like to join as a reviewer if you still need
Thank you @ajackley. Would you be interested in contributing to the writing? We already have reviewers, and would really appreciate it if you could help by co-authoring this chapter.
Hi @nrllh, Iβm happy to help in any capacity but I am less confident in an origination role. Perhaps a quick chat with one of the current/previous authors can help set expectations? Iβm in the Slack channel if anyone wants to DM me.
Hi @nrllh, Iβm happy to help in any capacity but I am less confident in an origination role. Perhaps a quick chat with one of the current/previous authors can help set expectations? Iβm in the Slack channel if anyone wants to DM me.
I sent you a DM on Slack
@bsmth since you told me you would like to fill empty spots in the project I wanted to ask you if you would be interested in contributing this chapter since it has promising amount of people and we have a few slots missing :)
@bsmth since you told me you would like to fill empty spots in the project I wanted to ask you if you would be interested in contributing this chapter since it has promising amount of people and we have a few slots missing :)
Thanks @burakguneli - sure, I can contribute as an editor here!
@bsmth that's amazing!!!
Sorry I wasn't successful in finding someone else :( But in the issue is stated, that there will be already a first meeting on 1st June, did I miss something? :(
there will be already a first meeting on 1st June, did I miss something?
Also curious, it would be great to sync up!
@martinakraus @bsmth @yohhaan @ajackley @JannisBush Unfortunately, we don't have any leads or analysts for this chapter. If any of you would like to volunteer to lead, we can address the lack of analysts. However, if no one is interested in leading the chapter, we might not be able to release this chapter for this year. Please if any of you are interested in leading let me know immidietaly and we can arrange an initial call to proceed quickly
Please if any of you are interested in leading let me know immidietaly and we can arrange an initial call to proceed quickly
I can't commit to leading the chapter, unfortunately, but I'd be happy to edit if someone has capacity ππ»
Hi @yohhaan @ajackley, since @ChrisBeeti has finalized the analysis, could you please take a look at it and start drafting the chapter? Thank you!
Hi @ChrisBeeti,
Can you check the comments I left on the results spreadsheets? and upload the 2025 queries to the cookies 2025 branch? (similar comment posted on Slack too).
Thanks!