Building a Better Foundation for This Site

One of the bigger challenges I kept running into wasn’t actually posting; it was keeping this site and TheTecnoAgrarian.com from drifting apart. Any time I fixed a bug on one, I had to remember to fix it on the other. Any small improvement meant doing the same work twice. It didn’t take long to realize that the problem wasn’t the posts themselves; it was the foundation underneath them.

Over the last few months, I rebuilt the backend of this site from the ground up. Not much looks different on the surface. You’ll notice the same layout and the same rhythm, but the entire engine underneath is new. The whole goal was to build something that stays reliable, consistent, and easy to update, no matter how much I add in the future.

A Workflow That Actually Works

The rebuild started with the idea of a shared “blog core” so both sites could run on the same foundation. That piece alone fixed most of my maintenance headaches. Instead of having two admin systems, two upload systems, two sets of middleware, and two separate places to fix the same bug, I now have a single, clean system that both sites share.

From there, curiosity took over. I built a custom analytics page so I could see what was happening without leaning on Google Analytics, and having that visibility made it easy to write my own bot blockers and IP rate limits to protect the site from unwanted automated traffic. I've built a better hero image upload process, so I’m no longer wrangling files. I set up an automatic backup system so both sites quietly protect themselves in the background.

Letting the Site Handle the Heavy Lifting

Along the way, I realized I could smooth out some of the bumps in my own posting workflow. Now, when I upload photos from my phone, the system automatically handles the formatting—compression, resizing, and converting everything into the right formats. That wasn’t the original driving factor, but it’s been a welcome side effect.


// From the image pipeline used by both sites
sharp(file.path)
  .resize({ width: 1600 })
  .webp({ quality: 80 })
  .toFile(finalPath);

All of this means fewer steps, fewer hiccups, and fewer things pulling me away from talking about what’s actually happening here on the property.

Why the Site Looks the Same

The design didn’t need a big overhaul. What I needed was stability something fast, predictable, and flexible enough to grow with us. Everything under the hood is cleaner and more reliable now, but the outside stays familiar, so the focus stays on the stories themselves.

What Happens from Here

With the backend sorted out and both sites running on the same engine, I’m able to shift back into sharing what’s happening here: the projects, the progress, the plants, the animals, and the slow work of building this place into what we want it to become.

If you want the technical version…

I put the full write-up over on TheTecnoAgrarian.com. That one goes into the shared core, the image pipeline, the analytics, the backups, and everything I learned while building it.

Coming Soon

I’m also starting a Raspberry Pi and Home Assistant YouTube series on our Fruition Forest Garden channel. This site will get the lived-in version of those projects, and the technical breakdowns will live on TheTecnoAgrarian.com.

It feels good to have the foundation built. Now I get to focus on the story again.