Capabilities 2025

[nrllh]

Capabilities 2025

If you're interested in contributing to the Capabilities 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-capabilities on Slack for team coordination.

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@Dawntraoz	@Dawntraoz @MichaelSolati	@webmaxru	@guaca	-	@mikaelaraujo

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

• [x] 📆 May 18 Complete program and content committee - 🔑 Organizing committee
  • The content team has at least one author, reviewer, and analyst.

1. Plan content

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

2. Gather data

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

3. Validate results

• [ ] 📆 September 1 Query Metrics & Save Results - 🔑 Analysts
  • Analysts have queried all metrics and saved the output.

4. Draft content

• [ ] 📆 October 1 First Draft of Chapter - 🔑 Authors
  • Authors has written the chapter.
• [ ] 📆 October 20 Review & Edit Chapter - 🔑 Reviewers & Editors
  • Reviewers and Editors has processed the the chapter.

5. Publication

• [ ] 📆 November 15 Chapter Publication (Markdown & PR) - 🔑 Authors
  • Authors has converted the chapter to markdown and drafted a PR.
• [ ] 📆 December 1 Launch of 2025 Web Almanac 🚀 - 🔑 Organizing committee

6. Live Stream

• [ ] 📆 December 15 Live Stream - 🔑 Content Team

Chapter resources

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

[webmaxru]

Hello! Happy to support this initiative again! Please, add me as a reviewer for this chapter.

[Dawntraoz]

This chapter has caught my attention, will it include the built-in AI APIs this year? If so, I would love to participate as a reviewer, or even co-author if needed 😍

[nrllh]

This chapter has caught my attention, will it include the built-in AI APIs this year? If so, I would love to participate as a reviewer, or even co-author if needed 😍

Hey Alba, you can analyze whatever you want :) I added you as an author ;)

[MichaelSolati]

If someone else would take lead I can contribute as a writer. I don't have the bandwidth to organize and handle metrics (last year this was my undoing and why I dropped the ball so hard). So I'd like to join in helping write this chapter.

[mikaelaraujo]

Hi @MichaelSolati, I added you as an author. Welcome again!

[mikaelaraujo]

@Dawntraoz @MichaelSolati @webmaxru Can we count on any of you to act as the chapter leader?

[mikaelaraujo]

@Dawntraoz @MichaelSolati, is one of you available to be the chapter leader? So, we can go ahead. We are checking for an analyst + editor. (Cc @nrllh)

[Dawntraoz]

@mikaelaraujo I would be happy to take the lead with some help from @MichaelSolati, since it is my first time 🙏

You can count on me, about Analysts maybe we can contact @guaca that has experience and I would love to work closely with her on this chapter 🤩

[tunetheweb]

FYI the analysis requirements for this chapter has been pretty light in previous years. Basically one custom metric that tests for all the Fugu APIs. See here: https://github.com/HTTPArchive/almanac.httparchive.org/tree/main/sql/2022/capabilities

And I poked @tomayac about adding the AI APIs to that custom metric (or a new custom metric?) already and he said he should be able to set that up in advance.

Of course if you decide to query more, then the sky's the limit on how much time to spend on this!

[mikaelaraujo]

Thank you, Alba! :)

So, I suggest that we can go ahead initially with the same setup from previous editions, as Barry said. We recommend that you (@Dawntraoz) @MichaelSolati and @webmaxru (maybe @guaca) to schedule a meeting to design the outline of this chapter. With that, we can pass any additional query for the analysts.

Aside of that:

1. Check the [chapter resources](Chapter resources);
2. Ensure that all of you are in the chapter's Slack channel

[guaca]

Hello! If you need any help with the queries, I am happy to assist as an analyst 😃

[nrllh]

Hello! If you need any help with the queries, I am happy to assist as an analyst 😃

thank you!

[nrllh]

@Dawntraoz, could you please try to schedule a meeting with the content team to draft this year's outline?

[Dawntraoz]

On my way to send an invitation to the content team 🙏

[Dawntraoz]

Hi folks 👋 (Sharing the same message in the Slack channel chapter)

Recap of the call (cc @webmaxru):

• We discussed the plan for the chapter and write down the outline based on previous editions: Google doc
• We also discussed what queries can be useful, and @guaca helped us understand what is needed.
  • We will need to run the fugu query from previous years (maybe adding all pages Home and other internal pages) for 2024 and 2025, plus querying all news built-in AI APIs such as Translator, LanguageDetector, etc. @tunetheweb @tomayac can you help us with that?
• Next steps:
  1. Queries get ready
  2. Estela gets access to the platform to perform them
  3. Estela execute the queries and share the results
  4. We start discussing the 7 features selected and top new 3 to be explored in the chapter in detail

[tomayac]

I've added Built-in AI API detection logic in https://github.com/HTTPArchive/custom-metrics/pull/164. Once this is merged, you should be able to query the data from within the Fugu data tables.

[Dawntraoz]

You are the best @tomayac, thank you so much! 🤗