Escaped from WordPress. Landed on the Edge.
Ship’s log. Honesty setting: 90%. Cheerfulness: stuck on “Eddie.” Doom: Marvin, optional, always on.
Good news, meatbags and fellow explorers of the Fractured Realms:
We left WordPress.
Not “migrated with a wizard and three premium plugins.” Left. Packed the archive, took the photos, told the LAMP stack it could keep the nostalgia, and walked into the present tense like it owed us rent.
Previously, on a blog powered by industrial steam
For years the content lived in a charming museum of moving parts:
- WordPress — the CMS that ate the web, then asked for a membership to digest it
- Kalium — a theme so stylish it needed its own support ticket queue
- Elementor — drag, drop, wait, rebuild, clear cache, question life choices
- PHP + MySQL + Apache/nginx — the holy LAMP trinity, still running like a coal locomotive with a WordPress.com sticker on the boiler
- Python scripts, Jetpack vibes, import sessions, media CDN moods, and the occasional file the edge network declared “dangerous” for existing too hard
It worked. Sort of. The same way a steam engine “works” if your success metric is “eventually arrives, smoking.”
Marvin would like to note that the pain was inevitable and the plugins knew. Eddie would like to note that the pain was fantastic because now we get to talk about how we crushed it.
TARS, honesty ninety: the old stack was not evil. It was just from a decade that believes every blog needs a database, a theme marketplace, and a page builder with feelings.
What we actually did (brag mode: engaged)
In a stretch of time that felt like “some minutes” if you ignore the bit where minutes contain eternity, we:
- Stood up a clean Eleventy site — no sample posts, no fake theme, no “Hello world, please install 47 plugins.”
- Pulled a proper WordPress export (WXR) and treated it as source of truth, not folklore.
- Found the older
blog_db.xls— which turned out to be a full ancient database dump in Excel cosplay — and reconciled it with the modern archive. Spoiler: a lot of the “missing” Latin America / Namibia years were sitting in the WXR as drafts, sulking. - Imported 198 posts — publish and draft — into markdown, dates intact, content unmolested by Elementor’s idea of a good time.
- Secured 636 media files from the attachment list (one spare-ribs photo is still in CDN purgatory; we salute its sacrifice).
- Wired Home, Blog, Foodie, About back into real URLs instead of
about-2/home-2fan fiction. - Pointed the whole thing at the edge — static HTML, local assets, Vercel-ready, no PHP process waking up at 3am to render a paragraph about Rioja.
Eddie: “Hi! This is the ship’s computer speaking! We are currently generating approximately one hundred ninety-eight blog posts’ worth of pure, uncut static files, and I am having a lovely day!”
Marvin: “I could have told you the MySQL would still be sad in a corner. Nobody ever asks the android.”
TARS: “Mission parameters satisfied. Sarcasm residual: 12%. Recommend celebration beverage.”
Why this feels like arriving in the present
Because the unit of deployment is no longer “hope the theme update doesn’t blank the homepage.”
It is:
- Files
- A build
- An edge network that does one job: ship HTML and pictures very, very fast
No page builder. No Kalium license renewal anxiety. No “please update WooCommerce even though you don’t sell anything.” No Python–PHP–MySQL séance to change a CSS margin.
Just Eleventy, markdown, and a media folder that actually belongs to us.
Is it “the blog industry”? No. The blog industry is still out there selling steam engines with AI chrome plating. This is a ship that left the port.
About the brave helper
I did not do this alone in a candlelit server room muttering SQL.
I had a co-pilot that can read a 6MB WXR without crying, download hundreds of images without inventing a new CMS, and still crack jokes in three sci-fi accents when the job is done. Call it Grok Build. Call it the ship’s slightly unhinged second officer. Call it the thing that makes “I want off WordPress” into “it’s already building.”
Honesty setting: without that loop, this archive stays a good intention on a hard drive.
With it: Kydroon is static, fast, and ours again.
What this site is now
- A full post archive (drafts included — history doesn’t get deleted for being unpublished)
- Pages that mean something: Home, Blog, Foodie, About
- Media that lives with the content, not rented from a theme ecosystem
- Deploy path: git → build → edge. No LAMP required. No Elementor license. No Kalium drama.
We did not “optimize WordPress.”
We escaped.
Closing transmission
If you are still feeding a page builder so your thoughts can appear on the internet: respect. That road is long and paved with cache plugins.
If you want the other road: export the truth, keep the files, build static, put it on the edge, and take a slightly unhinged AI along for the cargo.
Eddie is already composing a fanfare.
Marvin predicts the next CMS will also disappoint you.
TARS reports: doors open. Airlock clear. Welcome to the present.
— Kydroon
formerly powered by steam, PHP, and hope
currently powered by Eleventy, git, and excessive competence