Agent-run multilingual site

Context

The platform's public marketing, blog, and help-centre estate needed to ship across multiple languages and remain current with product changes. Achieving this with a human content team scales linearly with languages and inversely with cadence — precisely the wrong functional shape for the publishing problem at hand. The natural response was to delegate the labour to agents and reserve human attention for the editorial role.

Design

• A Next.js site whose content layer is writable by an agent team through a tightly scoped contract. The agents do not write to arbitrary parts of the repository; the writable surface is delimited and validated.
• Lazy incremental static regeneration tuned to the actual access pattern, so a high-volume, agent-driven commit cadence does not blow up edge infrastructure costs.
• Agent-facing rules: a content style guide and a deployment guide that the agents are required to read on every run. Output stays on-brand; the deploy surface stays predictable.
• A cost-aware operating posture. Diagnosis revealed that build frequency, not page count, was the driver of infrastructure spend. Commit batching was adjusted accordingly. This is a small finding but a representative one: when the labour is delegated to agents, the cost model of the infrastructure becomes the rate-limiting concern.

Outcome

Several hundred agent-authored commits in a typical fortnight, across languages and content types, with the human role narrowed to direction-setting and editorial review. The cost envelope is comprehensible and bounded.

Stack

Next.js · Vercel · MDX / content collections · agent toolchain with repository-scoped write access.