Crazy how much MB of JS are needed
- It's bloated with useless stuff for the users
AMP’s biggest advantage is the restrictions it draws on how much stuff you can cram into a single page.
As bullshit jobs exist, so do bullshit webpages
The authors think the url does not really matter anymore because
- they are not fully displayed in some browsers
- they need to be short and memorable to get people to it
So it does not need to contain a lot of information.
Some tricks the author uses and explains:
- using
<link rel="preload"
as="ROLE" href="URL">` to download - lazy-loading the search index (and this feature) as it is not used widely, and costs bandwidth (1.8MB)
- 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.
It looks interesting for new projects
- No link text
- Non-active element in tab order
- Missing link
alt
attribute - No
alt
text - Nested list not nested correctly
- Duplicate labels used
- Positive
tabindex
value - Invalid
aria-describedby
- No label for button element
- 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.
- Platforms aren’t forever homes
- SEO Writing is dead, storytelling is back
- Communities > Followers