JavaScript 2024

[nrllh]

JavaScript 2024

If you're interested in contributing to the JavaScript 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
@nrllh	@hadiamjad, @nrllh	@shubh401	@nrllh, @hadiamjad	@neriiavr	@tomvangoethem

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

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

2. Gather data

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

3. Validate results

• [x] 📆 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 JavaScript 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-javascript on Slack for team coordination

[neriiavr]

I'm interested being an editor

[NishuGoel]

Could author/co-author again either Javascript or the Performance chapter this year 🤩

[pooneh-nb]

I'm interested in contributing as an author or co-author for this chapter. Including any tasks related to analysis would be a great addition!

[kevinfarrugia]

I helped as the analyst last time round and would be happy to help again.

[hadiamjad]

I am interested in contributing to this chapter as an author or co-author. I would be happy to take on any analysis-related tasks as well.

[tomvangoethem]

It looks like we don't have a lead for this chapter yet. Are any of the authors interested in taking up that role? @NishuGoel, @pooneh-nb? A first step would be to set up a quick call with the different contributors of this chapters (preferably early this week) to align with everyone on the outline of the chapter. Thanks!

[kevinfarrugia]

This chapter already has two analysts so I will drop out. You could still reach me (here or on Slack) if you need a hand or have any queries from the last edition's queries. Thank you.

[hadiamjad]

Update on this?

[NishuGoel]

Sorry I am out! Can't find the capacity to dedicate time as an author here.

[nrllh]

Ok, we need to re-organize the content team. I'll lead the chapter for this year and replicate the analysis from the previous edition. I have already added the content from the previous edition to the doc. Please feel free to add your suggestions to the doc.