How we rebuilt this site: moving content out of the codebase

There are two ways to rewrite a corporate site: restyle it, or rethink where the content lives.

We chose the second, because this site will increasingly be maintained by AI. If articles live in the repository, every publish is a commit, a rebuild, and a deploy. That is fine when a human writes once a month. It is not fine when a machine writes twice a week.

Three decisions

First, articles go into Postgres. One post holds many translations under a single id, so language switching, hreflang, and the sitemap all come from one query.

Second, images go into object storage. Vercel's 250MB limit applies to the unzipped serverless function bundle, not static assets. But putting images in the repo still slows down clones and builds, and an AI cannot write a binary into git.

Third, publishing is decoupled from deployment. A publish calls revalidateTag and pages update in seconds without a redeploy.

The result

Publishing now looks like this: the agent calls the API, the row is written, revalidation fires. Under ten seconds end to end, with an audit record for every write.