So Apple destroys pianos with a hydraulic press, Microsoft invents TotalSurveillance™️ and Google tells us to put glue in our pizza and eat at least one rock a day.
Depuis quelques années, une partie de la communauté internet se tourne vers des solutions plus simples et moins gourmandes en ressources, en réaction à ce que beaucoup considèrent comme l’« #emmerdification » progressive du web. Le protocole #Gemini a émergé comme une réponse prometteuse à ce besoin, mais après l’enthousiasme initial, une certaine désillusion semble s’installer [...]
Code drunk, debug sober. Bah! Just fixed three bugs after a pint of Tundra.
(This is in no way meant to be role model behaviour. There just happens to be a lovely pub by the seashore in Bray where you can sit outside and it’s a nice distraction in the evenings when the weather is good and I don’t feel I’ve done enough in the day* and need a change of scene.)
It doesn’t help that I never think I’ve done enough in the day. 🤷♂️
「 In the same time library books have seen a lot. They were touched by a lot of greasy fingers, seen a lot of toilets. Just look at those two. Both are still fully usable, despite the tired look. 」
Kitten now has a lovely new multi-page Settings screen and… drumroll… a new 🐢 interactive shell (REPL) for you to play with the running state of your Small Web site/app/place and debug your app, inspect/manipulate its database, etc.
I plan on recording demos of each of them tomorrow but you can play with them now.
And here’s a little tutorial to get you started with the shell:
「 I am proudly introducing the first Omake on this site: User Friendly Archive. This adds over 5000 subpages, so I am now a webmaster of a significant website. 」
How do you make a modern website? Like this. No JavaScript, no databases, no frameworks. Just plain, simple, accessible, and fast HTML. You’d be surprised what you can get for $5/month.
Also, not immediately relevant to your current issue but something that might be worth considering for the future: using the htmx websocket extension, you can basically implement a streaming HTML approach (example using Kitten: https://ar.al/2024/03/08/streaming-html/) where you can just stream errors to the page as they happen.
Sitting outside on a rare sunny day at a lovely pub in Bray, refactoring Kitten* to pull out the settings page sections into their own pages (and use Kitten’s new Streaming HTML workflow**) and enjoying a yummy pint of Tundra IPA.
The Evergreen Web section in Kitten’s¹ settings now has its own page too (and uses Kitten’s new Streaming HTML² workflow).
If you have the previous version of your site up somewhere, you can use the 404-to-307 technique³ to forward missing pages to your old site so as not to break the Web.
“The simplicity of HTML and CSS now feels like a radical act. To build a website with just these tools is a small protest against platform capitalism: a way to assert sustainability, independence, longevity.” — Jarrett Fuller
I'm at an odd place with my personal website. Before Dec. 2023, it was a "professional portfolio" for my compositions. Now that I'm interested in the IndieWeb community, I want to make something more personal. I don't think I want to make two sites, but I do still need a portfolio for my composition work.
I just read @maggie's post on "digital gardens" and I really like that idea. (1/n)
I definitely want to add more pages, and once I add dropdowns within the menus, that'll be easier to organize. My main thing is that I don't know how to strike a balance of "personal" and "portfolio" in the content I put on my site.
Does anyone else have experience/thoughts on this? (2/2)