search

HTTPArchive / almanac.httparchive.org

HTTP Archive's annual "State of the Web" report made by the web community
https://almanac.httparchive.org
Apache License 2.0
603 stars 162 forks source link

Capabilities 2024 #3606

Open nrllh opened 4 months ago

nrllh commented 4 months ago

Capabilities 2024

Capabilities illustration

If you're interested in contributing to the Capabilities 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
@MichaelSolati @MichaelSolati @webmaxru, @shubh401, @christianliebel, @tomayac - - -
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

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

6. Virtual conference

Chapter resources

Refer to these 2024 Capabilities 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-capabilities on Slack for team coordination

webmaxru commented 4 months ago

Hello! Happy to be a reviewer for this chapter. I have experience with reviewing previous editions of Web Almanac

MichaelSolati commented 4 months ago

I'm happy to write this year.

nrllh commented 3 months ago

Hey @hemanth @beaufortfrancois @tomayac @christianliebel @jrstanley - awesome contributors from previous years 🙂 Are you interested in joining us again this year?

christianliebel commented 3 months ago

@nrllh I could help review this chapter. 😊

tomayac commented 3 months ago

@nrllh Also happy to review the chapter.

nrllh commented 3 months ago

Thank you, @christianliebel, @tomayac!

cqueern commented 3 months ago

@webmaxru @christianliebel @tomayac @shubh401 Looks like we've got plenty of reviewers but no analysts. Anyone fancy pivoting over to the analyst role?

tomayac commented 3 months ago

Anyone fancy pivoting over to the analyst role?

I'm not raising my hand, sorry, but here're some pointers for the person who decides to do so:

This should hopefully make your life easier!

MichaelSolati commented 2 months ago

@webmaxru @tomayac @christianliebel @shubh401 I'm about to email y'all a doodle to schedule a time for a content planning meeting. It'll probably go fast, but the fact we have no analyst is a small concern which hopefully we can iron out a plan for then. Check the emails you have listed on your GitHub profiles or message me if you don't get the email.

nrllh commented 1 month ago

@MichaelSolati, we can replicate the analysis from the previous edition. Can you please finalize the outline of the chapter ASAP?

nrllh commented 1 month ago

@MichaelSolati can you please give an update? Since we have no analyst in this chapter, I can replicate the queries of 2022.