Many small sites
People ask why my corner of the web looks like a small town instead of a single website. There's flessan.pages.dev, flessan.github.io, gdips.pages.dev, tune.thio.cc.cd, text.thio.qzz.io, and now this site at thio.cc.cd. This post is why.
Sites, not pages
A big website wants to be everything at once: portfolio, blog, shop, profile. It grows heavy, and every change risks breaking something else. A pile of small sites behaves differently:
- Each site has one job. GDIPS is a Geometry Dash server. teksreceh is a text toy. resontune is music. None of them pretend to be anything else.
- Each site can be rebuilt without evicting the others. When I learned React, then Rust, then Go, I started new sites instead of migrating a monolith.
- Old sites stay standing. flessan.pages.dev, my first little site, is still online. Old work is part of the work.
Learning by building
The deeper reason is simple: building real things is how I learn. Reading about Wayland teaches me a little. Building slate-de teaches me a lot. Every site in the pile started as a question - can a QR scanner be fully local? what does a GDPS need? can a text generator be a museum? - and became an answer you can visit.
A map of the pile
If you want to wander, the full list is on the ecosystem page. A quick tour:
- 🎮 gdips.pages.dev - GDIPS, the campfire
- 🎵 tune.thio.cc.cd - resontune, music without the paywall
- 🗿 text.thio.qzz.io - teksreceh, the text museum
- 🖥️ slate.dotfiles.qzz.io - slate-de, the d3sktop
- 📦 flessan.github.io - the project index
Every site has a door. Every door is open.