Fix 404s (#3885)

Author: tunetheweb

src/config/contributors.json

@@ -3131,7 +3131,6 @@
     "website": "https://blog.mgechev.com/"
   },
   "MiriamNaß": {
-    "github": "MiriamNaß",
     "name": "Miriam Naß",
     "teams": {
       "2024": [

src/content/en/2024/accessibility.md

@@ -281,7 +281,7 @@ Although ARIA landmarks have traditionally been only visible to screen reader us
     {{ figure_link(
       caption="Landmark element and `role` usage (desktop).",
       sheets_gid="1224962143",
-      sql_file="llandmark_elements_and_roles.sql",
+      sql_file="landmark_elements_and_roles.sql",
     ) }}
   </figcaption>
 </figure>
@@ -858,7 +858,7 @@ The following map shows the average desktop accessibility score by country top l
   description="In looking at Top Level Domains with more than 45,000 domains, we learn about accessibility. Displayed visually in a world map the most accessible countries are Norway, Filand, Canada, USA, UK, Sweden, Ireland, Australia, New Zealand, Austria, Belgium, Switzerland, Denmark, and South Africa. China is the least accessible by Top Level Domain. ",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQ32BLKultx6YJbcQP5DB6a4NTnf4h9RCC3QXte5oS-Onx-9cFqiPQ23dWgWgffj2QA1Q60zhrxJVYb/pubchart?oid=783736776&format=interactive",
   sheets_gid="1209052596",
-  sql_file="lighthouse_score_by_tld"
+  sql_file="lighthouse_score_by_tld.sql"
   )
 }}
 
@@ -870,7 +870,7 @@ But it is a bit easier to see the TLD ranked and including the non-country codes
   description="A bar cart with looking at Top Level Domains with more than 45,000 domains, we learn about accessibility. Displayed as a bar chart with the accessible domains .edu (Education), .gov (US Government), Norway, Filand, .io, Canada, USA, .app, UK, Sweden, Ireland, Australia, New Zealand, .co, Austria, Belgium, Switzerland, Denmark, and South Africa, .org.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQ32BLKultx6YJbcQP5DB6a4NTnf4h9RCC3QXte5oS-Onx-9cFqiPQ23dWgWgffj2QA1Q60zhrxJVYb/pubchart?oid=783736776&format=interactive",
   sheets_gid="1209052596",
-  sql_file="lighthouse_score_by_tld"
+  sql_file="lighthouse_score_by_tld.sql"
   )
 }}
 

src/content/en/2024/cms.md

@@ -333,7 +333,7 @@ The Lighthouse <a hreflang="en" href="https://web.dev/performance-scoring/">perf
   description="Bar chart showing the median CMS Performance score for WordPress is 61 on desktop and 38 on mobile, Wix is 85 and 55 respectively, Squarespace 60 and 30, Joomla 58 and 39, Drupal 65 and 40, Duda 80 and 59, 1C-Bitrix 51 and 33, Weebly 71 and 33, TYPO3 CMS 65 and 47, and finally for Tistory it's 54 and 29.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=2144802411&format=interactive",
   sheets_gid="14177383",
-  sql_file="lighthouse_scores_per_cms.sql",
+  sql_file="lighthouse_category_scores_per_cms.sql",
   width=600,
   height=559
   )
@@ -357,7 +357,7 @@ As we've concluded in previous years, the lower mobile scores are an opportunity
   description="Bar chart showing the year on year CMS Performance score over 2023 and 2024. WordPress was 33 in 2023 and 38 in 2024, Wix was 50 and 55, Squarespace 28 and 30, Joomla 35 and 39, Drupal 36 and 40, Duda 56 and 59, 1C-Bitrix 31 and 33, Tilda 36 and 37, TYPO3 CMS 42 and 47, Weebly 32 and 33",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=270170798&format=interactive",
   sheets_gid="1754565121",
-  sql_file="lighthouse_scores_per-cms_yoy.sql",
+  sql_file="lighthouse_category_scores_per_cms_yoy.sql",
   width=600,
   height=559
   )
@@ -377,7 +377,7 @@ A CMS and content on it is generally set up to serve as much information to sear
   description="Bar chart showing the median CMS SEO score for WordPress is 92 on desktop and 92 on mobile, Wix is 100 and 100 respectively, Squarespace 92 and 92, Joomla 92 and 92, Drupal 85 and 85, Duda 92 and 92, 1C-Bitrix 92 and 92, Weebly 85 and 91, TYPO3 CMS 92 and 92, and finally for Tistory it's 92 and 85.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1386400078&format=interactive",
   sheets_gid="14177383",
-  sql_file="lighthouse_scores_per-cms.sql",
+  sql_file="lighthouse_category_scores_per_cms.sql",
   width=600,
   height=559
   )
@@ -393,7 +393,7 @@ The median SEO scores in the top 10 platforms range from 85-100, an impressive i
   description="Bar chart showing the year on year CMS SEO score over 2023 and 2024. WordPress was 90 in 2023 and 92 in 2024, Wix was 97 and 100, Squarespace 93 and 92, Joomla 88 and 92, Drupal 85 and 85, Duda 86 and 92, 1C-Bitrix 86 and 92, Tilda 91 and 100, TYPO3 CMS 89 and 92, and finally Weebly 85 and 91",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=61098748&format=interactive",
   sheets_gid="1754565121",
-  sql_file="lighthouse_scores_per-cms_yoy.sql",
+  sql_file="lighthouse_category_scores_per_cms_yoy.sql",
   width=600,
   height=559
   )
@@ -415,7 +415,7 @@ Each accessibility audit is either a pass or a fail, but unlike other Lighthouse
   description="Bar chart showing the median CMS Accessibility score for WordPress is 86 on desktop and 86 on mobile, Wix is 95 and 94 respectively, Squarespace 93 and 94, Joomla 83 and 83, Drupal 86 and 85, Duda 89 and 88, 1C-Bitrix 75 and 75, Weebly 86 and 86, TYPO3 CMS 84 and 84, and finally for Tistory it's 78 and 74.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=476143776&format=interactive",
   sheets_gid="14177383",
-  sql_file="lighthouse_scores_per-cms.sql",
+  sql_file="lighthouse_category_scores_per_cms.sql",
   width=600,
   height=559
   )
@@ -431,7 +431,7 @@ In 2024, the median Lighthouse accessibility score for the top 10 CMSs ranges be
   description="Bar chart showing the year on year CMS Accessibility score over 2023 and 2024. WordPress was 87 in 2023 and 86 in 2024, Wix was 94 and 94, Squarespace 92 and 94, Joomla 84 and 83, Drupal 87 and 85, Duda 88 and 88, 1C-Bitrix 77 and 75, Tilda 81 and 84, TYPO3 CMS 86 and 84, and finally Weebly 86 and 86.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=476143776&format=interactive",
   sheets_gid="1754565121",
-  sql_file="lighthouse_scores_per-cms_yoy.sql",
+  sql_file="lighthouse_category_scores_per_cms_yoy.sql",
   width=600,
   height=559
   )
@@ -458,7 +458,7 @@ By following these best practices, developers can enhance both the functionality
   description="Bar chart showing the median CMS Best Practice score for WordPress is 78 on desktop and 79 on mobile, Wix is 78 and 79 respectively, Squarespace 100 and 96, Joomla 78 and 79, Drupal 78 and 79, Duda 78 and 79, 1C-Bitrix 56 and 57, Weebly 56 and 57, TYPO3 CMS 96 and 96, and finally for Tistory it's 74 and 79.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=1321714408&format=interactive",
   sheets_gid="14177383",
-  sql_file="lighthouse_scores_per-cms.sql",
+  sql_file="lighthouse_category_scores_per_cms.sql",
   width=600,
   height=559
   )
@@ -476,7 +476,7 @@ While most other CMSs show worse numbers in the best practices audits, TYPO3 CMS
   description="Bar chart showing the year on year CMS Best Practice score over 2023 and 2024. WordPress was 92 in 2023 and 79 in 2024, Wix was 92 and 79, Squarespace 92 and 96, Joomla 83 and 79, Drupal 83 and 79, Duda 92 and 79, 1C-Bitrix 75 and 57, Tilda 83 and 79, TYPO3 CMS 92 and 96, and finally Weebly was 83 and 57.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vQYh0RHAqp768faimbvZpvS71yJwCaOAFR0AzgotkEphtxphBKR1kt-pqgxA8Uxj4FSii1RQWwgG6rk/pubchart?oid=10302778&format=interactive",
   sheets_gid="1754565121",
-  sql_file="lighthouse_scores_per-cms_yoy.sql",
+  sql_file="lighthouse_category_scores_per_cms_yoy.sql",
   width=600,
   height=559
   )

src/content/en/2024/fonts.md

@@ -64,7 +64,7 @@ To understand the font hosting choices made by web developers, we follow the met
   description="Column chart showing the percentage of pages making requests to hosts in 2024. Non-exclusive self-hosting is at 70% of pages for both mobile and desktop. Exclusive self-hosting is at 28% for desktop and 34% for mobile. Self-hosting with a service is at 43% for desktop and 36% for mobile. Non-exclusive service usage is at 60% for desktop and 51% for mobile. Pages using services exclusively is at 19% for desktop and 16% for mobile.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vTHmcrit1gMzxfZNeFp9LrA4NQSMEh140fapD4CFQ89knpy6LvEKz7VafGaFGlxCAxTdpLZXaVaq8Pg/pubchart?oid=835212931&format=interactive",
   sheets_gid="1014103088",
-  sql_file="performance/service.sql"
+  sql_file="performance/fonts_services.sql"
   )
 }}
 

src/content/en/2024/security.md

@@ -1429,7 +1429,7 @@ Large websites often have a high number of visitors and registered users, of whi
   description="Bar chart showing in top 1,000 sites, 64% have XFO, 60% have HSTS and 56% have X-Content-Type-Options headers. In top 10,000, 54% have XFO, 46% have HSTS and 54% have X-Content-Type-Options headers. In top 100,000, 51% have XFO, 42% have HSTS and 50% have X-Content-Type-Options headers. In top 1,000,000, 45% have XFO, 36% have HSTS and 47% have X-Content-Type-Options headers. Among all sites, 29% have XFO, 31% have HSTS and 43% have X-Content-Type-Options.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vTxTTMlFFSMT3mZgw2awA0wl3F68gzU1OLuyMaZXscSFq-Pa5ev_qTXx8ZaGEOl_ox_aHsraAGMXZ9Y/pubchart?oid=256464807&format=interactive",
   sheets_gid="434545590",
-  sql_file="header_use_by_rank.sql",
+  sql_file="security_adoption_by_rank.sql",
   width=600,
   height=505
   )
@@ -1447,7 +1447,7 @@ In some industries, developers might keep more up to date with security features
   description="Bar chart showing the top 5 and bottom 5 of the average number of security headers per category. Shopping has an average of 1.80 security headers, Finance has 1.71, Beauty & Fitness has 1.70, Home & Garden has 1.66, and Computers & Electronics has 1.65. People and Society has an average of 1.48 security headers, Books & Literature has 1.45, Real Estate has 1.40, News has 1.38, and Travel & Transportation has 1.34.",
   chart_url="https://docs.google.com/spreadsheets/d/e/2PACX-1vTxTTMlFFSMT3mZgw2awA0wl3F68gzU1OLuyMaZXscSFq-Pa5ev_qTXx8ZaGEOl_ox_aHsraAGMXZ9Y/pubchart?oid=139345565&format=interactive",
   sheets_gid="1042348266",
-  sql_file="feature_adoption_all_party_by_category.sql",
+  sql_file="feature_adoption_by_category.sql",
   width=600,
   height=617
   )

src/content/en/2024/structured-data.md

@@ -33,7 +33,7 @@ Over the past 18 months, there have been significant changes in the structured d
 
 2. **Enhanced existing types**: Improvements to organization data, product variants, and the introduction of discount-rich results.
 
-3. **Structured data carousels**: The beta launch of structured data carousels, combining `ItemList` with other types, opens new content presentation possibilities on Google's SERP ([source](https://developers.google.com/search/blog/2023/05/carousels-beta)).
+3. **Structured data carousels**: The beta launch of structured data carousels, combining `ItemList` with other types, opens new content presentation possibilities on Google's SERP ([source](https://developers.google.com/search/docs/appearance/structured-data/carousels-beta)).
 
 4. **GS1 integrations**: There has been increased support for GS1 standards such as the <a hreflang="en" href="https://www.gs1.org/standards/gs1-digital-link">GS1 Digital Link</a>, which aims to bridge the gap between physical and digital product information. This technology enables manufacturers and retailers to connect physical products to their digital identities through QR codes. When scanned, these codes provide access to comprehensive product information, enhancing transparency and customer engagement. Also, the `gs1:CertificationDetails` property has been officially adopted by Google as `schema:Certification`, demonstrating how industry-specific extensions can successfully influence and integrate with Schema.org standards.
 
@@ -50,7 +50,7 @@ As the structured data ecosystem matures, we're witnessing a diversification in
 1. **Schema.org as markup**: The traditional method of embedding structured data directly into webpages continues to be a cornerstone of modern SEO practices.
 
 2. **Schema.org as a data standard**:
-  Beyond its use in HTML, Schema.org is increasingly employed to standardize data shared via APIs or feeds. For example, Google's <a hreflang="en" href="https://datacommons.org/">Data Commons</a> initiative uses an extended Schema.org vocabulary to integrate datasets from hundreds of organizations globally. This standardization supports tasks like dataset discovery and relationship mapping, crucial for understanding provenance, subsets, and derivations of datasets in AI-driven environments (<a hreflang="en" href="https://research.google/blog/relationships-arecomplicated-an-analysis-of-relationships-between-datasets-on-the-web/">source</a>).
+  Beyond its use in HTML, Schema.org is increasingly employed to standardize data shared via APIs or feeds. For example, Google's <a hreflang="en" href="https://datacommons.org/">Data Commons</a> initiative uses an extended Schema.org vocabulary to integrate datasets from hundreds of organizations globally. This standardization supports tasks like dataset discovery and relationship mapping, crucial for understanding provenance, subsets, and derivations of datasets in AI-driven environments (<a hreflang="en" href="https://research.google/blog/relationships-are-complicated-an-analysis-of-relationships-between-datasets-on-the-web/">source</a>).
 
 3. **Semantic data in social web applications**:
 
@@ -65,7 +65,7 @@ Structured data plays a key role in emerging regulatory requirements like the EU
 
 As AI-powered search engines, chatbots, and conversational assistants continue to expand their reach, structured data plays a pivotal role in enhancing content discoverability and contextual understanding across these platforms. Key examples include:
 
-  - **AI Search Engines**: Platforms like Bing Chat and Google AI Overview utilize structured data not only to train their language models but also to deliver contextually rich and accurate responses. By leveraging structured data, these systems can interpret complex relationships between datasets, improve search relevance, and enable users to seamlessly navigate interconnected datasets (<a hreflang="en" href="https://research.google/blog/relationships-arecomplicated-an-analysis-of-relationships-between-datasets-on-the-web/">source</a>).
+  - **AI Search Engines**: Platforms like Bing Chat and Google AI Overview utilize structured data not only to train their language models but also to deliver contextually rich and accurate responses. By leveraging structured data, these systems can interpret complex relationships between datasets, improve search relevance, and enable users to seamlessly navigate interconnected datasets (<a hreflang="en" href="https://research.google/blog/relationships-are-complicated-an-analysis-of-relationships-between-datasets-on-the-web/">source</a>).
 
 These capabilities demonstrate structured data's evolving role in not only improving discoverability but also in enhancing AI systems' ability to interpret and act on relationships between data, thereby creating richer and more useful user experiences.
 

src/content/en/2024/sustainability.md

@@ -685,7 +685,7 @@ The case of carousels remains contentious: users, developers, and designers tend
 
 For arguments against using carousels, visit:
 - <a hreflang="en" href="https://shouldiuseacarousel.com/">Should I Use A Carousel</a>
-- <a hreflang="en" href="https://www.smashingmagazine.com/2023/08/designing-better-carousel-ux/">Usability Guidelines For Better Carousels UX</a>
+- <a hreflang="en" href="https://www.smashingmagazine.com/2022/04/designing-better-carousel-ux/">Usability Guidelines For Better Carousels UX</a>
 
 If animations are necessary for your design:
 - Use CSS animations where possible, as they're generally more performant than JavaScript-based animations.

src/content/it/2022/css.md

@@ -753,7 +753,7 @@ Abbiamo anche dato un'occhiata ad un paio di valori delle proprietà `flex` e `g
 
 Il valore del contenuto per la proprietà `flex-basis` è un'istruzione esplicita al browser di guardare alla dimensione del contenuto intrinseco dell'elemento, piuttosto che a qualsiasi larghezza impostata sull'elemento stesso. È un valore recente, al momento in cui scrivo non disponibile nella versione di rilascio di Safari. Attualmente, solo lo 0,5% dei siti mobili e lo 0,6% dei siti desktop utilizzano questo valore.
 
-Il valore `subgrid` per `grid-template-rows` e `grid-template-columns` è, al momento dell'indagine, supportato solo da Firefox. Forse non sorprende notare che compare solo in 211 pagine mobili e 212 desktop nell'intero set di dati. Dal momento che il valore fa parte del progetto [Interop 2022](./interoperabilità), sarà interessante vedere come crescerà il supporto una volta diventato interoperabile.
+Il valore `subgrid` per `grid-template-rows` e `grid-template-columns` è, al momento dell'indagine, supportato solo da Firefox. Forse non sorprende notare che compare solo in 211 pagine mobili e 212 desktop nell'intero set di dati. Dal momento che il valore fa parte del progetto [Interop 2022](./interoperability), sarà interessante vedere come crescerà il supporto una volta diventato interoperabile.
 
 ### `Box-sizing`
 

src/templates/en/2024/methodology.html

@@ -519,10 +519,5 @@ <h2 id="looking-ahead"><a href="#looking-ahead" class="anchor-link">Looking ahea
       <p>
         The {{ year }} edition of the Web Almanac is the fifth in what is mostly an annual tradition (we took a break in 2023) in the web community of introspection and a commitment to positive change. Getting to this point has been a monumental effort thanks to many dedicated <a href="{{ url_for('contributors', year=year, lang=lang) }}">contributors</a> and we hope to leverage as much of this work as possible to make future editions even more streamlined.
       </p>
-
-      {# TODO - uncomment if we want to include this #}
-      <p class="hidden">
-        If you&#8217;re interested in contributing to the 2025 edition of the Web Almanac, please fill out our <a hreflang="en" href="https://forms.gle/??">interest form</a>. Let&#8217;s work together to track the state of the web!
-      </p>
     </section>
 {% endblock main_content %}