📣 Contribute to the 2022 Web Almanac

[rviscomi]

Hi @HTTPArchive/almanac-contributors, please join us for the 2022 Web Almanac, our fourth edition!

At this early stage, we're starting with assigning teams of contributors to each chapter. A chapter's content team consists of authors, reviewers, analysts, and editors. See this discussion for more info about how authors are selected.

ℹ️ To get involved, choose a chapter from the list below and reply to its respective issue to indicate which role(s) you'd be interested in. You can also filter issues for those labelled "2022 chapter" and "help wanted" to see what's available.

Here's the current lineup for 2022:

Page Content

• CSS
• JavaScript
• Markup
• Structured Data
• Fonts
• Media
• WebAssembly
• Third Parties
• Interoperability 🆕

User Experience

• SEO
• Accessibility
• Performance
• Privacy
• Security
• Mobile Web
• Capabilities
• PWA

Content Publishing

• CMS
• Ecommerce
• Jamstack
• Sustainability 🆕

Content Distribution

• Page Weight
• Resource Hints now under Performance
• CDN
• Compression
• Caching
• HTTP

⚠️ Are there any other major topics on the web that we're missing? Any suggestions to organize the content differently? I'd love to hear your ideas in the comments.

For all chapter-specific questions/discussions, head over to the issues linked above.

And if you're interested to contribute to the project beyond a specific chapter, there are also opportunities to join the translators, developers, and designers teams!

The Web Almanac is supported entirely by the web community, so thank you all for your interest and support to keep this valuable resource going year after year!

---

If you know which chapter you'd like to join, no need to reply to this discussion. Head over to the chapter's tracking issue and leave a comment indicating what role you're interested in!

[daKmoR]

would it make sense to have a dedicated section for web components? or where would they fall into?

[daKmoR]

things I can think of from the top of my head

• websites having at least one customElement defined
• average numbers of customElements if (at least one is defined)
• average javascript size/loading time of websites using at least one customElement
• how many websites are using shadow dom
• how many websites are using declarative shadow dom
• how many websites are using constructible stylesheets
• which web component libraries are used the most
• ...

hmmm I guess there could be enough content - what do you think?

PS: I am however not sure if these numbers are available? 🤔

[rviscomi]

I think there's some good data there but it might not be substantive enough to support its own chapter. The 2021 Markup chapter had about 35 metrics, for comparison. I'd suggest merging this with Markup for now and we can revisit this later if we find that there's sufficient data.

[GregBrimble]

Does the Jamstack chapter plan to include discussion about some of the newer web frameworks which start to blur the lines (e.g. Remix, SvelteKit, Qwik and Astro)?

[bkardell]

@rviscomi in markup in 2019 we started counting all 'non-standard elements' and using tools that used that collected data to classify 'dasherized' elements, but I don't think that then or since we have actually attempted to collect actual calls to define. That could be interesting because I am sure there is quite a mismatch between "I'm just using a safe element name I can find and style" vs "this is actually a custom element". shadow roots would be interesting to know but unless the client has some special privileges, is it fully detectable? Just looking for .shadowRoot on everything won't work, will it? I think even that is not exposed if it is a closed root.

[rviscomi]

@bkardell that's a great question. I don't know enough about how custom elements are defined to say how feasible it'd be to detect but let's continue exploring that in the Markup chapter.

[rviscomi]

(forking to a new comment thread) @GregBrimble said:

Does the Jamstack chapter plan to include discussion about some of the newer web frameworks which start to blur the lines (e.g. Remix, SvelteKit, Qwik and Astro)?

Nothing has been planned yet. A quick check of Wappalyzer shows that all of the example frameworks are indeed being detected already, which is great. I'd suggest accessing the Jamstack 2022 planning doc and adding any ideas to the outline section. As the team fills out you can continue iterating on the outline.

I've also put your name down as a reviewer for now in the Jamstack issue #2898.

[SaptakS]

I wonder if there is scope for a chapter on Indieweb. I am not sure it will have enough data tobe it's own chapter, but might be interesting to see how many websites are integrating indieweb features such as microformats, webmentions, etc.

[nhoizey]

This would be really great indeed! 😍

[rviscomi]

Perhaps we could incubate this topic in the Structured Data chapter and split it out if it turns out that there's enough content?