I took over the US site and web-coded it solo

The build lives on my laptop

I stood up the site's Next.js project locally and drive every change through AI-assisted web coding against a real dev server. I self-check each change visually on localhost before it leaves my machine. I built it without a front-end engineer or Webflow.

One sentence starts a release round

Every round runs the same way. I clone the latest main into a new dated folder, rename the previous round with a -published-donotuse suffix and keep it on disk, edit and self-check on localhost, write the changelog and bump the version, then push and announce. Doing that by hand is twenty minutes of setup before any actual work, every time, and it is the kind of procedure a person eventually starts shortcutting.

So the SOP became an agent workflow that remembers the procedure. I say one line, that we are preparing an update, and it runs the chain: builds a clean folder, pulls the current main from GitLab, installs and prepares the local environment, applies the naming law, and carries my locally tested changes into the new merge request untouched. Two checks run inside it. One agent verifies that anything I changed in the shared global configuration cannot reach the Japanese or Korean sites. A technical-SEO agent runs new content against our own checklist. Then it uploads to GitLab, writes the changelog, and drafts the channel message. I built that release agent the same way as the reusable agent teams behind this work.

The last step is the one that keeps it honest. The merge request it just pushed becomes the working base for the next round, and the previous folder is archived automatically. My local copy is therefore never more than one version behind main, which is what stops the slow drift that makes a hand-run process rot.

Pulling Japan and Korea out of our blast radius

Underneath all of this, I separated the global configuration. Japan and Korea sit in subfolders of the English site and inherited a lot of shared settings, which meant we could not move fast here without shaking them. I split the shared layer so their configuration stands on its own. The skeleton and the visual system still line up across all three, deliberately, and each region now has room to differ.

The US ships first as the pioneer: we build a thing, ship it, and find out where it breaks. Japan and Korea then adopt it on their own schedule rather than having it pushed onto them mid-release. When I later built the CMS, that is how it went: stand it up in their environment, hand over an account, and let them adjust within their own global settings for local reading habits and visual conventions, with no risk of their changes landing on anyone else's site. It works in the other direction too, since they can quickly copy, translate and localize a configuration we ship here.