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
602 stars 164 forks source link

Jamstack 2024 #3610

Open nrllh opened 4 months ago

nrllh commented 4 months ago

Jamstack 2024

Jamstack illustration

If you're interested in contributing to the Jamstack 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
@mneumegen @mneumegen @thomkrupa @guaca - @turban1988
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 Jamstack 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-jamstack on Slack for team coordination

ianand commented 4 months ago

What is the definition of "Jamstack" that the 2024 version of the almanac will use? The official definition (Jamstack.org) has shifted over the years, as has the definition used by the web almanac. In 2020/2021 it was a framework-centric definition and in 2022 it was performance-centric definition.

nrllh commented 4 months ago

What is the definition of "Jamstack" that the 2024 version of the almanac will use? The official definition (Jamstack.org) has shifted over the years, as has the definition used by the web almanac. In 2020/2021 it was a framework-centric definition and in 2022 it was performance-centric definition.

Thank you for sharing your concern. We are focused on the framework-centric domain; however, the analysis and outline are shaped by the content team.

nrllh commented 3 months ago

@ianand, would you be interested in contributing as an author?

S3gillu commented 3 months ago

Would love to contribute as a reviewer for jamstack

nrllh commented 3 months ago

Hey @seldo @whitep4nth3r @GregBrimble @Nutlope @seldo - awesome contributors from previous years 🙂 Are you interested in joining us again this year?

seldo commented 3 months ago

I appreciate the invitation, but it doesn't really fit my current job description!

Nutlope commented 3 months ago

Likewise, I will pass thank you!

whitep4nth3r commented 3 months ago

I'm afraid I don't have capacity this year, but I'm sharing this with someone who I think might be up for it.

mneumegen commented 3 months ago

hey @nrllh, I've been working on a community project to figure out where Jamstack goes from here, happy be involved if I can be useful.

nrllh commented 3 months ago

Thank you, @mneumegen! So you are now the lead autor ;) We need an analyst and a reviewer, then we are fine with this chapter!

thomkrupa commented 2 months ago

Hey, I'm happy to review the content. I'm already in touch with @mneumegen, and we need to catch up and talk about Jamstack—it is his initiative. I think he is the right person to be the lead author for this topic.

I'm the co-founder of a Jamstack agency, and we've been working on a lot of Jamstack-related projects, so I can share my perspective on how the term Jamstack evolves for us and our clients.

nrllh commented 2 months ago

Thank you, @thomkrupa!

Do you (@thomkrupa, @mneumegen) think you could also take on the role of analyst for this chapter? Unfortunately, we still do not have any analysts.

mneumegen commented 2 months ago

Is there any documentation of the data and analyst tools available? I'm new to this so I'm not quite sure what I'm getting into taking on a whole chapter.

tunetheweb commented 2 months ago

Mostly we query the HTTP Archive dataset which is based on a monthly crawl of the top X million websites in the world. It gathers all the stuff that makes up the homepage (what resources it loads, the size of those… etc.), and one secondary page. For both mobile simulation and desktop simulation. It also runs a Wappalyzer detection to try to detect what technologies are used by the site based on JS it sees, HTTP headers and HTML markup. All this data is stored in a massive BigQuery dataset.

There’s an Analyst’s guide here: https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide

And the 2022 queries are here if you can read SQL: https://github.com/HTTPArchive/almanac.httparchive.org/tree/main/sql/2022/jamstack

At its simplest you can copy and paste the queries to a 2024 folder and update the dates. And then run them through BigQuery (we’ll provide access to that as some of these queries are chunky!).

For a more interesting chapter, it’ll mean seeing what new stuff you can query for. That’s a brainstorming exercise between the author, the analyst and reaching out to some HTTP Archive experts (including myself) to see what’s possible. For example, In 2022 they went in a whole new direction as to what they defined as a Jamstack. You can continue that, or revert to 2021 definition and queries. Or come up with something new again!

And if there’s stuff that’s not available that you can pick up from the page using JavaScript the you can write that script and we’ll help you get it added to the next crawl so you can gather that data. So JavaScript knowledge would be good if that’s needed. Or alternatively you can update our technologies detection config to catch and new technologies we’re not detecting.

So read the previous years chapters to familiarise yourself with the type of stuff that can be queried. Then ask yourself what you as a Jamstack subject matter expert would like to know on the topic? What did previous years not cover that would be interesting to dig into?

You can also browse the other chapters to see what they include to further understand what’s possible, and maybe give inspiration.

guaca commented 2 months ago

Hi there!

I'm happy to join as an analyst 😃

BTW, I love @tunetheweb's suggestion about brainstorming to see what new things we can query for 👍

ianand commented 2 months ago

@ianand, would you be interested in contributing as an author?

Sorry for the delay. Realize it's a moot point now but I didn't have the bandwidth. Glad to see @mneumegen is on it though! Curious to see what you come up with given the past approaches and challenges.

nrllh commented 2 months ago

Sorry for the delay. Realize it's a moot point now but I didn't have the bandwidth. Glad to see @mneumegen is on it though! Curious to see what you come up with given the past approaches and challenges.

thank you, @ianand! We are still looking for contributors for this chapter. Please let us know, if you want to contribute to the chapter =)

mneumegen commented 2 months ago

Let's do it @guaca & @thomkrupa. I've sent a Calendar event for next week to talk about first steps. @turban1988 & @S3gillu if you're keen to join, send an email over to mike@cloudcannon.com.

Thanks!