A project leant to curate web content online. It is only an archive by now.

The Open Directory Project's goal is to produce the most comprehensive directory of the web, by relying on a vast army of volunteer editors.

It was so simple, anyone who wanted to could create a free account [on Geocities, Tripod, FortuneCities, or Freeservers and build a website to share their hobbies and ideas.

The web was more about browsing and exploration.

It is worth remembering a website [...] can also be art. The web is also a creative and cultural space that [can be Free from convention defined by commercial product design and marketing].

If the commercial web is "industrial", you could say that the small web is "artisanal". One is not better than the other. They serve different needs and both can co-exist in an open web.

There is a lot of old good website, internet archive links and examples

age.xml is a free and easy-to-use website label that gives parental control systems information about a website’s age rating

(via https://nicolas-delsaux.hd.free.fr/Shaarli/shaare/LMJ21Q)

Use vanilla HTML/CSS
Don't minimize that HTML
Prefer one page over several
End all forms of hotlinking
Stick with native fonts
Obsessively compress your images
Eliminate the broken URL risk

About the web of the 90s:

Many people had personal web sites, usually published on GeoCities, where exploring the web was a fun adventure that was not fuelled by algorithms.

The Web 1.0 died because search engines prioritzed other contents. In some ways it is good because we get far more accurate search results. On the other hand, it's all about the money and tracking.

How to turn it positive?

Use social media sparsely: quit Facebook, Instagram and others. Look forward for decentralised alternatives like Mastodon. Break the dopamine addiction and turn off all notifications from social media. Familiarize yourself with POSSE and make your site the single source of truth for all your content online.

Discovering Web 1.0 through neocities: a modern implementation of GeoCities.
There are also other website aggregators such as personalsit.es.

Look for a blogroll on personal websites you come across. If you own a website, add one!

Des traductions françaises de Slash Pages.

The browser provides a default text size based on user preferences, and our text should be relative to that preference. Establishing our root font-size with an em value helps keep that relationship intact.

About the definition of one rem:

I really do want sites to usually just give me text around 24px (or ‘large’), because that’s a pretty good default for me.

Sites with smaller body text would ideally increase their font size, but sites with the same size or larger text certainly shouldn’t get even bigger.

Yes I share this assumption.

I slightly better approach:

html {
  font-size: clamp(1em, 0.9em + 1vw, 1.5em);
}

A love letter to the personal website

A reflection of your personality in HTML and CSS (and a little bit of JS, as a treat). This could be a professional portfolio, listing your accomplishments. It might be a blog where you write about things that matter to you. It could even be something very weird and pointless (even better) – I love a good single-joke website. Ultimately, it's your space and you can do whatever you want with it. It can be a single-joke website.

On the other side, it is now intimidating to be a newcomer now with all these frameworks. They skip right over the basics.

The website we use today for fun are also businesses. They need an account to view the content. They have a barrier to entry.

Your website, your rules. There's no reply guys on your own website if you want to. it doesn't have the downsides of Twitter.

You can be a creator anywhere on the internet these days, but there's only a small handful of places where you actually own your own content. Your own website is one of them.

Now AI is generating slop. During the talk, Maggie asks: is there a future in which we need to have some kind of "reverse Turing test" to prove our humanity on the internet?

The whole point of WWW is to be decentralised and independent. It was released as an open standard so that access could be as democratic as possible.

To bring the WWW spirit back, we can carve out our own individual spaces on the web. HTML is accessible, and there are many web services to build websites nowadays. So why aren't we doing it? we don’t build websites for ourselves like we used to, we build them for the audiences we want.

Try something. For the nerds: try out. The site deploys in less than 30s. Try new CSS things as lomng as you rely on progressive enhancement.

The personal site isn't dead. It's just been forgotten in the commercialised, capitalist web of today. We owe it to ourselves to rediscover this lost art. [...] So, once again my digital call to arms: build your own website. Make it fun. Make it pointless. But most importantly: make it yours.

Appendix: look at these cool websites

An example of /supporters page for the slash pages

My tasks at work has me looking up the two-letter country codes a lot recently. My goto is the ISO-3166-1 alpha 2 page on Wikipedia, but getting there involves a few clicks, a web-search, and a “find on page.” I wanted an easier way to get to this list, and a much easier way to filter it. I also wanted something that could work as a Vivaldi side panel, so that I can call it up while I’m looking at something else.

The web page: https://2lcc.lmika.app/

• das Projekt wird mit dem UI-Library auf Gedeih und Verderb ausgeliefert
• Wie gut passen sie zur eigenen Corporate Identity beziehungsweise zum eigenen Corporate Design?

wir eher davon abraten würden, eine solche Library einzusetzen, einfach um zu vermeiden, dass man sich in eine große Abhängigkeit begibt, sich den Weg in die Zukunft verbaut und sich die Möglichkeit für individuelle Anpassungen nimmt.

Aus eigener Erfahrung kann ich sagen, dass dies zum einen gar nicht so teuer ist, wie viele immer annehmen, und dass die größten Kosten in Bezug auf Mobile, Accessibility und so weiter nicht in der Implementierung, sondern in der Konzeption der Benutzerführung anfallen. Und diese Kosten entstehen ja ohnehin, ob nun mit oder ohne UI-Library.

Es ist oft gar nicht so sinnvoll, auf eine UI-Library zu setzen, sondern man sollte viel häufiger eigene UI-Komponenten entwickeln. Das ist sehr viel weniger aufwendig als oft angenommen. Und der Vorteil ist: Man hat die volle Kontrolle, bleibt flexibel, bleibt unabhängig und vermeidet langfristig zahlreiche Probleme.

UI-Libraries können gut passen, wenn sie 100% zu den Anforderungen passen.

A blog post.
An RSS feed for it.
An index.html.

Then more blog post.

How a webpage can work for everyone

An index of the web!

Curlie strives to be the largest human-edited directory of the Web. It is run by volunteer editors. Join today to add to our collection or create your own!