Some tricks the author uses and explains:

1. using <link rel="preload" as="ROLE" href="URL">` to download
2. lazy-loading the search index (and this feature) as it is not used widely, and costs bandwidth (1.8MB)
3. Reducing the cost of webfonts: shrinking the typeset of the font (especially for titles) + combining css files

The author reduced the page load from 11 seconds to 4 seconds with these.

There’s a standard way to make part of a page not visible until the user requests it: the

tag. You may have seen this on big code examples in some of my other posts.

I wanted to show the types of webpages that could be added to your website, making it feel fuller, more interactive, and substantial

Which WCAG criteria concerns the projet phase, component, device, usw...?

A similar community to the Yesterweb, small web, etc...

a project to excavate shut down, abandoned web ruins and restore them to surfable, visually accessible, searchable, remixable condition

somewhere between a library and a living museum, we're working on experimental new ways to close the gap between archival and visibility of the web that was lost

A solarpunk web is the goal of the cheap web.

Cheap is different from free, sleek, creep, deep and dark.

How to build a cheap web? KISS and sustainable. Some tools are listed, as well as examples in the "explore" part.

I like to think about websites along two axes:

• Static vs. dynamic — how much of the page updates in response to user interaction?
• Online vs. offline — how much functionality requires a persistent Internet connection?

I like the quadrant that can be built with that: every site I know can be put in it.

An /about page built with the heart

See how this could be easily implemented with links, <dialog> or <buttons> in HTML5. The web made progress.

Pour le menu, plaçons le sur une page dédiée,

Pas con: si toutes les pages sont légères et mises en cache, alors la navigation sera tout aussi fluide. Le menu peut très bien être une page en lui-même.

Another ode to the web

It looks interesting for new projects

1. No link text
2. Non-active element in tab order
3. Missing link alt attribute
4. No alt text
5. Nested list not nested correctly
6. Duplicate labels used
7. Positive tabindex value
8. Invalid aria-describedby
9. No label for button element
10. Invalid aria-labelledby

Before the social media craze or publishing platforms, and long before ‘content creator’ was a job title, blogs served as one of the primary forms of online expression and communication. [...] We had webrings, forums, and carefully curated link pages instead.

At their core, they all have one characteristic in common: they’re there because their owners wanted to carve out their space on the internet. And I think you should do the same. Let’s talk about why that is.

1. Platforms aren’t forever homes
2. SEO Writing is dead, storytelling is back
3. Communities > Followers

With the latest changes in MacOS, we can now build Progressive Web Apps for all devices.

The web of things is built on the web of documents, which is built on the web of computers controlled by Domain Name owners, which itself is build on a set of interconnected cables. This is an architecture which provides a social backing to the names for things. It allows people to find out the social aspects of the things they are dealing with, such as provenance, trust, persistence, licensing and appropriate use as well as the raw data. It allows people to figure out what has gone wrong when things don't work, by making the responsibility clear.

The value of this architecture is that each layer leverages the social components of the lower layer's architecture

• Universality
• Open Standards
• Open Web Platform (OWP)
• Open Government through Open Data
• Openness with personal data on the Social Net
• Open Platform
• Open Source
• Open Access
• Open Internet and Net Neutrality

Too many websites could generate nice reports as documents, but had no way to access the data behind it to check and build on the results.