Welcome to this blog
Why a blog in 2026 when you already have an online business card? To write without a platform or a tracker, from tech to video games, confessions included.
For a while now, my digital business card has held my email address and my online profiles. Great for finding me, useless for reading me. I was missing a place of my own to dig into the things I care about, free from any platform, its algorithm, or its ads. This blog is that place. And as tradition demands, its first article is about... the blog itself1.
Why write here
Social networks chop thoughts into confetti, and a thread vanishes as fast as it showed up. A text on your own domain will still be readable in ten years. Which cuts both ways, sure, since my mistakes will age just as gracefully.
I'll write about tech in the broad sense, the project management I do for a living, video games, and a few less tidy confessions, hence the "private diary left wide open" on the home page. No editorial calendar, either. I'll write when I have something to say, which also happens to be the world's best excuse for going quiet. French comes first, English second, and every article exists in both.
Under the hood
The site is fully static. It's built with Astro, which replaced Eleventy in September, and styled with Tailwind CSS, with no client-side framework at all. In plain terms, your browser gets HTML, one stylesheet, and a few small comfort scripts, not an app with delusions of grandeur. Fonts are self-hosted, code highlighting is baked in at build time by Expressive Code, and search runs on Pagefind, whose index is also built ahead of time.
To write an article, I drop in a Markdown file that looks like this.
---title: Welcome to this blogdescription: Why this blog exists and how it's built.date: 2026-06-10tags: - blog---
The content starts here.Everything else takes care of itself, since the CI pipeline builds the site and ships it to my server on every push. A lot of engineering to, in the end, publish text. You get the idea2.
Creature comforts
I spent time on the small things that make reading pleasant, and this article doubles as the demo.
| Feature | Where to see it |
|---|---|
| TL;DR and table of contents | At the top of the article |
| Reading progress bar | At the top of the screen |
| Footnotes | Along the way |
| Search and archives | In the footer |
On top of that, you get a dark theme, an estimated reading time, an RSS feed per language, a copy button on code blocks, and images served in several sizes, as AVIF whenever your browser plays along.
And your privacy
There's almost nothing to declare. No account, no cookies, no ad trackers, not one request to a third-party service. I only count visits with an anonymous tool running on my own server, the equivalent of a foot-traffic counter at a bookstore door. The privacy policy spells it all out, with admirable seriousness for a document that has almost nothing to regulate. Read here the way you'd read a book a friend lent you, no library card, nobody looking over your shoulder.
What comes next
New articles will show up at their own pace. The RSS feed is there if you want them delivered. And if one of them makes you want to talk back, my business card lists every place you can do it, praise and pushback equally welcome. The diary is open. Now I just have to keep writing in it.