atelier. Your website is almost here!

Your website is almost here! · section 1

Your website is almost here!

Your website is almost here!

Ditching WordPress during a two-hour meeting

Oh no!

A few minutes before a two-hour meeting I wanted to look something up on my booklog, boeken.tsuk.org, a site I have been keeping (on and off) since 2002. What I got instead was a cheerful Dreamhost placeholder page — boeken.tsuk.org is almost here! — and, underneath, helpfully: Upload your website to get started.

The website had been there for close to twenty years.

A browser showing boeken.tsuk.org serving a Dreamhost placeholder page: 'boeken.tsuk.org is almost here! Upload your website to get started.' A browser showing boeken.tsuk.org serving a Dreamhost placeholder page: 'boeken.tsuk.org is almost here! Upload your website to get started.'
Figure 1 The crime scene, a few minutes before a two-hour meeting: the Dreamhost placeholder where the booklog used to be, inviting me to get started.

Some digging in my spam folder later I discovered Dreamhost's security systems had decided the site was hacked and being used for phishing, and had responded the way you'd child-proof a house you never intend to enter again: by spraying .htaccess files into literally every folder, locking visitors out of all of it. Eh.

DreamHost's abuse notification email, redacted: the site has been disabled for suspected phishing, citing a file from 2018. DreamHost's abuse notification email, redacted: the site has been disabled for suspected phishing, citing a file from 2018.
Figure 2 The abuse notification, fished out of the spam folder (redacted where needed)..

I was a little worried at first, but that quickly gave way to "I'm not angry I'm just disappointed", and once the initial oh come on subsided, I was actually mostly relieved: this was the eviction notice the site had been waiting years for.

The patient

Boeggn — tagline: Altijd al een boeklog willen bijhouden, "always wanted to keep a booklog" — is a book log in Dutch. A page per book read (if I finish the book, if I find the time to write a short review, if the site isn't dying on me, if I don't forget it, if I can actually be bothered): a cover, a rating, a paragraph or three or ten of what I thought of it. The first entry is dated 21 August 2002; the most recent, when the lights went out, late May 2026. In between: 889 published books, 567 approved comments, 1,367 uploaded images, and 2,764 post revisions.

The old Boeggn home page: a reverse-chronological list of book reviews in the custom WordPress theme. An old Boeggn book page: cover, rating, free-text publication line and review in the custom WordPress theme.
Figure 3 The site as it was some time before that Tuesday morning, as recovered from the archive.org: the home page and a book page, in the custom WordPress theme I built somewhere around 2011 and had been carefully not touching since.

The "on and off" was often more off than on. Plot the entries per year and you get less a publishing schedule than a polygraph readout of two and a half decades: one book in 2002, silence, a trickle in 2009, then 138 in 2011 and an almost implausible 248 in 2012, tapering through the twenty-teens to exactly one book in 2023, then back up to 86 in 2024.

(Rest assured that my OCD did not allow me to not keep a list of books read.)

100 200 1 1 21 138 248 122 55 69 30 29 3 58 12 1 86 14 1 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
Figure 4 Entries per year, 2002–2026. The gaps are the point: the chart doubles as an autobiography of the book log.

Technically, the site was a custom WordPress theme I built myself, with lots of gaffer tape and chewing gum keeping the parts somewhat connected, running on a shared Dreamhost server that had felt, for years on end, like a mosquito swimming in honey (hence the drop-offs when WordPress became unmanageably slow and the spurts when it mysteriously became a little faster again). The site was still there because Dreamhost was cheap, because moving it was hassle, and because I certainly didn't feel like digging into that theme again and making it work in some more elegant way than it did. Inertia is a perfectly serviceable hosting strategy, and in my experience most problems tend to go away when you ignore them long enough, ahem.

This is a quick write-up about the work I/we did today. A lighter story than the one about my father's thesis: nothing here needed a vision model or an editorial conscience, just a spine, a database dump, and some free time during a meeting. In order: strangler-fig rebuild ftw; stuff I found in the database; the redesign I had been putting off for years; the author data, which turned out to be the actual rabbit hole; and what the site is like to live with now (but actually not — see the update).