CSS 2025

[nrllh]

CSS 2025

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

Content team

Lead	Authors	Reviewers	Analysts	Editors	Coordinator
@bartveneman	@bartveneman, @GeekBoySupreme	@svgeesus @bartveneman @GeekBoySupreme	-	@GeekBoySupreme	@turban1988

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 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 css 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-css on Slack for team coordination

[bartveneman]

Hi, creator of projectwallace.com here. I'd love to contribute in some form as a reviewer or analyst. Especially since last year's CSS chapter got scrapped. The almanac has shaped some analysis decisions I've made on my website so I consider this a modest 'payback'. 🤗

[svgeesus]

Happy to be a reviewer

[turban1988]

Thanks @bartveneman @svgeesus for your support!

[GeekBoySupreme]

I would love to help review and/or edit this chapter. I helped write the CSS chapter way back in 2021 and haven't been able to help better with this project. Happy to jump in and help.

[turban1988]

I would love to help review and/or edit this chapter. I helped write the CSS chapter way back in 2021 and haven't been able to help better with this project. Happy to jump in and help.

Great! Thanks!

[bartveneman]

One thing I hadn't really accounted for is the level of SQL knowledge required for the analyst role. Upon reading the role descriptions I think I'd be a better author or editor. Apologies for not preparing better before submitting.

[turban1988]

No worries I marked you as an author

[turban1988]

@carmenansio @hemanth @j9t @nrllh @rvth @dereknahman, are you interested in contributing to this year's edition?

[GeekBoySupreme]

Hey @bartveneman, let me know if you need some help while writing the chapter as well. Since I am helping review and edit, probably worth it to be involved in a bit of the writing too.

[nrllh]

@bartveneman, since you were the only author, I've assigned you as the lead for this chapter - hope that’s okay. @GeekBoySupreme, thank you! I've assigned you as a co-author, your help with the writing is very welcome.

[bartveneman]

I've added the outline to the planning doc

[bartveneman]

I've had very little comments so far, so I'm unsure how to move forward with this chapter. I'd really hate it if we'd miss deadlines or not get a chapter at all, so if there's anything I can do to make concrete steps in getting this chapter done I'd love some pointers.

[nrllh]

@bartveneman If your outline does not require any custom metrics, you are good. If that’s not the case, you probably won’t be able to have the analysis (via planed custom metrics), since we cannot ensure that custom metrics will be merged in the next crawl.

The CSS chapter is one of the most comprehensive chapters of the Web Almanac. It would be great to have at least two analysts for this chapter who can run the analysis by the next deadline, September 1. If we cannot find analysts for this chapter, it will be at risk :(

[bartveneman]

I have defined a lot of custom/new metrics so that' sgoing to be a major roadblock in my narrative. Since I'm the creator or projectwallace.com is there a way to get a hold of the raw crawl data so I can process the CSS by myself? Then I can act as an analyst using OSS projects to create reproducible results. I know that's a long shot but I just want this chapter to happen and not fall back to 'old' metrics for ages.

[tunetheweb]

I have defined a lot of custom/new metrics so that' sgoing to be a major roadblock in my narrative.

Since we gather ALL the CSS usage (using Lea's Rework CSS) this may not be as big a deal to collect the data as much of it is probably already being collected anyway. But it would require someone to write and run the queries. You can see the 2022 queries here and most will simply require a year update and a run to get 2025 data. For new metrics many likely just need a copy and a paste one of the example queries and a slight tweak to query the new data.

Since I'm the creator or projectwallace.com is there a way to get a hold of the raw crawl data so I can process the CSS by myself? Then I can act as an analyst using OSS projects to create reproducible results. I know that's a long shot but I just want this chapter to happen and not fall back to 'old' metrics for ages.

The data is in the publicly available parsed_css BigQuery table so if you know a bit of SQL then yes. See the Analyst Guide for more details and make sure you get added to the HTTP Archive group to expense your queries cause this is a LOT of data and expensive to query.

[bartveneman]

Okay, thanks for the insights! We're about to find out if that Bachelor of Computer Sciences holds any value.

[tunetheweb]

Happy to answer any questions and guide you through the first few queries! Though I'm less familair with the parsed_css table to be honest.

[bramus]

I've had very little comments so far, so I'm unsure how to move forward with this chapter.

I can take a look and have requested commenter’s access on the doc

[svgeesus]

I've had very little comments so far, so I'm unsure how to move forward with this chapter.

I commented early on, but had few comments. Please interpret that as "it all looks good to me, except as noted".

[bramus]

Left some comments and added some more ideas for things to track. One thing I find missing is perhaps a section on custom fonts / the usage of @font-face. Would be nice to gather some data around that as well.

[bartveneman]

I commented early on, but had few comments. Please interpret that as "it all looks good to me, except as noted".

Great points, thank you!

Left some comments and added some more ideas for things to track. One thing I find missing is perhaps a section on custom fonts / the usage of @font-face. Would be nice to gather some data around that as well.

Some excellent new data points or deeper dives, I'm up for that. Thanks!

[turban1988]

Hey guys, I quickly wanted to check in on the status of this chapter. Can we assist you in any way?

[bartveneman]

Due to the loss of a close friend recently I haven't been able to dive into generating queries yet. Some help in that area would be very helpful.

[svgeesus]

If we have crawl data already, it would be great to know real-world usage of color(rec2020 ...) because CSS WG is currently considering a small but non-backwards compatible change to bring the spec in line with current implementations

• https://github.com/w3c/csswg-drafts/issues/12574

[svgeesus]

But it would require someone to write and run the queries. You can see the 2022 queries here and most will simply require a year update and a run to get 2025 data. For new metrics many likely just need a copy and a paste one of the example queries and a slight tweak to query the new data.

I notice that the 2022 queries for color syntax are missing some values. for example lab and lch are there but oklab and the popular oklch are missing. I gues that should be simple to copy-paste-edit to fix.

[asdaraujo]

I can help rewriting and running the queries for 2025, if no one is working on that yet.

[nrllh]

Hey @asdaraujo, thank you, that would be great! Can you please join our channel for this chapter (💬 #web-almanac-css)?

[bartveneman]

That'd be awesome @asdaraujo. I'm happy to hop on a call for more details about the queries necessary and how they help writing the chapters. The Slack channel would be a great start for that 😄

[asdaraujo]

Hey @asdaraujo, thank you, that would be great! Can you please join our channel for this chapter (💬 #web-almanac-css)?

@nrllh I need either an invitation from the channel admin, so that I can join with my own email, or a @httparchive.org email to join the channel. I don't have either at the moment :)

[asdaraujo]

That'd be awesome @asdaraujo. I'm happy to hop on a call for more details about the queries necessary and how they help writing the chapters. The Slack channel would be a great start for that 😄

@bartveneman That would be great. I see you're in the Netherlands. I'm in Australia, so your early mornings would work well with my early evenings. Please let me know what's your availability.