And now, imagine that this place is your personal website, under your own domain name, under your control.
This is the basic idea behind the IndieWeb.
Most tools and ideas of the IndieWeb is Publish Own Site, Syndicate Elsewhere.
Another is Webmentions.
Good job!
— Permalink
Similar to Days since last Facebook scandal, but for Web 3.
— Permalink
Another blogging platform
— Permalink
Create a web design based on Code Lyoko graphics
— Permalink
]]>It seems that many of the products Google actively encourage web authors to add to their sites are paradoxically the ones that have the worst impact on performance.
The amount of data they collect goes far beyond what is useful to the end user, and is undoubtedly a contributor to the huge proportion of “junk data” stored in datacentres worldwide.
I recently made the case for this at work while making improvements to the company website, and my manager admitted that they rarely look at the analytics.
— Permalink
It seems to be a cool web project to extend HTML to the backend.
— Permalink
Still competitions on the web, but without fragmentation.
We want to make it easier for developers to track the list of features that are widely available and those that are under development.
To contribute:
Exactly the project I wanted to build: display URL informations and their names.
— Permalink
How to link webmentions.io messages, likeCount, replyCount and reportCount to a personal blog with a few JS lines.
— Permalink
Crazy how much MB of JS are needed
— Permalink
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
— Permalink
The authors think the url does not really matter anymore because
So it does not need to contain a lot of information.
— Permalink
Some tricks the author uses and explains:
<link rel="preload"
as="ROLE" href="URL">` to downloadThe 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.
— Permalink
]]>I wanted to show the types of webpages that could be added to your website, making it feel fuller, more interactive, and substantial
— Permalink
Which WCAG criteria concerns the projet phase, component, device, usw...?
— Permalink
A similar community to the Yesterweb, small web, etc...
— Permalink
]]>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.
— Permalink
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.
— Permalink
An /about page built with the heart
— Permalink
See how this could be easily implemented with links, <dialog>
or <buttons>
in HTML5. The web made progress.
— Permalink
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
— Permalink
alt
attributealt
texttabindex
valuearia-describedby
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.
With the latest changes in MacOS, we can now build Progressive Web Apps for all devices.
— Permalink
]]>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
— Permalink
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.
— Permalink
Hypertext systems should take about 1/4 second to move from one place to another. If the delay is longer, people may be distracted; if the delay is much longer, people will stop using the system. If the delay is much shorter, people may not realize that the display has changed.
It is funny how thoughts about speed and user experience were already there before the 2000's.
Issue: Links on the web are often quite slow
]]>One solution is to abandon hypertext links. [...] Have a one-page view.
Another strategy is to exchange one large delay for many small ones. We can sometimes arrange a Web site to to bundle large parts of the data in a package that is pre-loaded at the entrance. Within the site, link response is quick because time-consuming sound, graphic, video, and applets have been pre-loaded onto the user's computer.
A better solution, for sophisticated hypertexts that must provide crisp performance, may be to use the Web as a way to provide access to, and information about, hypertexts that can be downloaded (or purchased) as a unit and then performed on the user's machine.
Thoughts of the web and hyperlinks
— Permalink
]]>eine neue Literaturgattung, bei der sich die tradierten Strukturen von Erzählungen in offene, für den Leser unerwartete Strukturen auflösen. Vielfältige Rezeptionswege werden durch die Möglichkeit, im Text zu springen, möglich. Der Leser wird dabei durch seine Auswahlentscheidungen zum Mitproduzenten des Textes.
— Permalink
(In context of web gardening)
]]>Highways are judged by efficiency: distance, cost, safety, and time. Garden paths play a different role; they lead us through the best routes, not the shortest. They may bend to pace our journey, curving here to reveal a view, twisting there to lead us through a shady grove or a sunny clearing.
— Permalink
]]>Rigid hypertext is streetscape and corporate office: simple, orderly, unsurprising. We may find the scale impressive, we admire the richness of materials, but we soon tire of the repetitive view. We enter to get something we need: once our task is done we are unlikely to linger. We know what to expect, and we rarely receive anything more.
— Permalink
Make an OSS version of it for the web: why not building on the web for the web?
— Permalink
]]>At times, wilderness is exactly what readers want: a rich collection of resources and links. At times, rigid formality suits readers perfectly, providing precisely the information they want, no more and no less. Indeed, individual hypertexts and Web sites may contain sections that tend toward each extreme.
Often, however, designers should strive for the comfort, interest, and habitability of parks and gardens: places that invite visitors to remain, and that are designed to engage and delight them, to invite them to linger, to explore, and to reflect.
— Permalink
A website about web, links and hypertext... well it is a garden when someone can lost itself a bit.
— Permalink
Baseline is a new term that defines a feature broad adoption. There are two stages:
We can then speak of baseline 2023 that groups all features usable in the considered browsers.
Limitations:
I like the model: Subject - Predicate - Object
Such as: Xerxes - Parent - Brook.
It can be modeled as such:
parent(xerces, brooke).
parent(brooke, damocles).
]]>Note of Tim Berbers-Lee.
Put a frame around "engineering" and " ownership"
— Permalink
]]>The overwhelming motivation behind it seemed to be “I made something, here it is”. Sharing things for the sake of showing them to the world. Somebody had created something, then put it online so you could see it. Visit their website (wait for the dial-up to finish), and it’s yours.
Large companies find HTML & CSS frustrating “at scale” because the web is a fundamentally anti-capitalist mashup art experiment, designed to give consumers all the power. — Mia, with valuable secrets 🤫 (@TerribleMia) November 24, 2019
You can stand out of the crowd by simply treating the web platform as what it is: a way to deliver content to people.
The best growth hack is still to build something people enjoy, and then attach no strings to it. You’d be surprised how far that can get you.
— Permalink