THE LEAVING WORDPRESS CASE STUDY

Lighter
Without
It.

First published

For years WordPress was how I built websites. In the autumn of 2026 I took every one of them off it, one site at a time. Nothing was lost on the way. What went was the weight.

See what changed
Five sites · one direction
  • montynetwork.com26 Oct
  • montysoundsradio.com3 Nov
  • montyphotostudios.com12 Nov
  • montysounds.com12 Nov
  • vfml.netinto the Lounge
Seventeen days. No plugins left to update.
01 / OVERVIEW

Overview

Between 26 October and 12 November 2026, every WordPress site in Monty Network was rebuilt or retired. Four were rebuilt as small, fast sites of my own, published straight from GitHub to Cloudflare. The fifth, the vfml.net journal, was folded into Monty Lounge.

It's part of Monty Network, and like the rest of the network the work was planned, built and checked by one person: me.

This case study covers why I left a tool I'd used since the early days, the one pattern every site followed, how each old address was kept, what replaced the plugins, and what the network looks like now that WordPress has gone.

02 / AT A GLANCE

Leaving WordPress at a Glance

Five sites. One pattern. Every address still answering.

5WordPress sitesFour rebuilt, one retired into Monty Lounge
17DaysFrom the first site live on 26 October to the last on 12 November 2026
0PluginsNothing left to update, patch or renew
13WebsitesEvery public site in the network, all custom-built
Published from GitHubServed by CloudflareOld addresses keptEnglish and PolishBuilt-in SEOHealth check for Monty ControlPrivate statsNo admin login to attack
03 / PERSONAL STORY

Why I Left

I've been designing websites since the early 1990s, and for a long time WordPress was how I built them. It was quick to start, it did a lot out of the box, and when photography became my hobby in 2021 and the sites began to multiply, it carried them all.

But each site brought its own plugins, its own updates and its own login. Pages carried code they never used. A site that was, at heart, a single button for a radio station loaded like a magazine.

Over the same years I'd learnt to build things myself: Monty Control, the apps, the new montynetwork.com. Next to them, WordPress began to feel bulky and limited: a coat that no longer fitted.

Not turning my back on it.

WordPress taught me a great deal. Leaving it isn't a verdict on where I started. It shows how far the work has come.

04 / THE CHALLENGE

The Challenge

Moving a site is easy. Moving it without anyone noticing is the hard part. Every move had to:

  • keep every old address working, because search engines, short links and old posts all point at them
  • keep the look visitors know, or improve it, never lose it
  • speak English and Polish, like the rest of the network
  • be watched by Monty Control from the first minute, with health checks, link scans and stats
  • happen alongside everything else, by one person, without a weekend of downtime

The answer was not five clever moves. It was one plain pattern, repeated five times.

05 / ONE PATTERN

One Pattern, Five Times

Every site left WordPress the same way. Once the pattern worked for one, the next was mostly a matter of content.

  1. A repositoryOne site, one GitHub repository of its own
  2. A small buildPlain HTML, or a light generator, and nothing the page doesn't use
  3. A test addressLive on Cloudflare's own address first, shared by a temporary short link
  4. The switchThe domain moves over, and the old site steps aside

Before the switch, each site gets the same checklist:

  • Search basics. Titles, descriptions, canonical addresses, preview cards for social media, structured data, a site map and a proper "not found" page.
  • Two languages. The round gold EN and PL buttons, with every page in both languages.
  • A health check. A small file Monty Control reads to know the site is well.
  • Private stats. The Monty Stats script, which counts visits without collecting anything personal.

Publishing is a push to GitHub. Cloudflare builds the site and puts it live in a few minutes. There's nothing to upload by hand, and every version of every page is kept.

06 / SITE BY SITE

Site by Site

The order mattered. The hub went first, so every other site had somewhere solid to link back to.

SiteLeft WordPressWhat it became
montynetwork.com26 Oct 2026The network's front door, built by a small script of my own in four days, now with case studies and project pages in two languages
montysoundsradio.com3 Nov 2026A single-button radio player styled after the TV app: 51 commits from first sketch to live
montyphotostudios.com12 Nov 202643 one-page photography guides and six longer articles, each on its old address
montysounds.com12 Nov 2026The music's front door: ten collections, the SoundCloud catalogue and the radio, in English and Polish
vfml.netNov 2026Retired. Its journal now lives in Monty Lounge, alongside the photographs and the music

The WordPress control panel that once managed all of them was retired too. Its address now leads to Monty Control.

The new montysoundsradio.com on a laptop: the studio picture fills the screen, with the Now Playing card and the Play Live Radio button on the right
montysoundsradio.com, the first site rebuilt after the hub. The Monty Sounds Radio case study tells its story in full.
07 / EVERY ADDRESS KEPT

Every Address Kept

An address is a promise. Somewhere there's a search result, a bookmark or a post from last year pointing at it. Breaking it breaks that promise quietly, and you never find out who was let down.

  • Photography guides keep their names. On montyphotostudios.com, /aperture/, /shutter-speed/ and the DJI Pocket 2 guide all live exactly where they did on WordPress. The few that moved have a redirect waiting.
  • Collections never change their address. On montysounds.com every collection page has a fixed address, because my short links point straight at them.
  • Short links follow the content. A short link's destination can be changed in one place, so links already shared on social media keep landing in the right spot.
  • Old journal links land somewhere useful. The vfml.net journal's readers are pointed to Monty Lounge rather than an error page.
The new Monty Photo Studios guides page: 43 single-page guides in four topics, each a printable sheet
The new guides page on montyphotostudios.com: 43 guides, every one on the address it always had.
08 / WHAT REPLACED THE PLUGINS

What Replaced the Plugins

Plugins weren't the enemy. Each one solved a real problem. The question was whether the problem still needed a plugin once the site was built properly.

On WordPress

  • An SEO plugin for titles, previews and the site map
  • A backup plugin, with copies on its own server
  • Logins to protect on every site
  • Forms and widgets from different makers
  • A control panel to keep every site updated

Now

  • Search basics written into every page as it's built
  • Every version kept on GitHub, plus the host's daily backup and a mirror drive
  • No admin login on the public sites at all
  • Monty Chat on the pages, my own, one design
  • Nothing to update: a push to GitHub is the update

The pages carry only what they use, so they're lighter and quicker on a phone. And there's less to go wrong at three in the morning, because there's simply less there.

09 / KEEPING WATCH

Keeping Watch

A move isn't finished when the site is live. It's finished when Monty Control can see it.

  • Health. Each new site answers a health check, and an outside monitor watches it around the clock.
  • Links. The Link Checker crawls every site on its weekly rota. On 12 November its list of WordPress sites became empty, and its WordPress section was removed.
  • Basics. A nightly round of site checks covers the things a move can quietly break: the site is up, its certificate is valid, its home page tags are in place, and its robots file and site map can be read.
  • Stats. Every new site reports to Monty Stats from day one, so the before and after can be compared.

How all of that works together is its own story: the network that watches itself.

10 / WHAT STAYED

What Stayed

Not everything moved, and that was deliberate.

  • The hosting account. It still runs Monty Control and the scheduled jobs that keep the network ticking overnight. Those jobs are being given a new home of their own in Monty Cron, one at a time.
  • The content. Every guide, collection and journal entry came across. Only the machinery underneath changed.
  • The look. Dark, gold and Monty the shih tzu, on every site, as before.
Visitors shouldn't be able to tell that anything moved. Only that it got quicker.
11 / RESULTS

Results

On 12 November 2026 the last WordPress site went quiet. The network that's left is smaller underneath and bigger on the surface.

0WordPress sitesAcross the whole network, from 12 November 2026
43Guides on their old addressesMonty Photo Studios moved without breaking a link
2LanguagesEnglish and Polish on every rebuilt site except the English-only guides

Each site now has one place where it lives, its GitHub repository, and one way to change it. When something needs fixing, I know exactly where to go.

Figures as of 12 November 2026, from the sites' repositories and Monty Control.

12 / WHAT'S NEXT

What's Next

  • Scheduled jobs, rehomed. Moving the overnight jobs into Monty Cron, so the network keeps its own time.
  • More to read. Monty Lounge carries the journal on, with travel, photographs and music side by side.
  • The same pattern for whatever comes next. Any new site starts the way these ended: one repository, a small build, a test address, then the switch.

Where to see it

What I've learnt

The heaviest part of a website is often the part nobody sees. Take it away, and what's left is the site you meant to build in the first place.

Same sites. Less weight.

Stuck with a heavy WordPress site? I rebuild sites the same way: fast, plugin-free, every address kept. I build bespoke.

Contact us ↗