-
-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JavaScript 2024 #3592
Comments
I'm interested being an editor |
Could author/co-author again either Javascript or the Performance chapter this year 🤩 |
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! |
I helped as the analyst last time round and would be happy to help again. |
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. |
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! |
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. |
Update on this? |
Sorry I am out! Can't find the capacity to dedicate time as an author here. |
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. |
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
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 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
The text was updated successfully, but these errors were encountered: