Blog
Notes on multilingual content, MDX, and AI translation.
- A CMS built for AI agentsAI agents read, edit, and review content best as plain files in git. How schema validation, inline tokens, and static exports turn a content repo into something an agent can safely maintain.
- Multilingual SEO in Next.js: hreflang, sitemaps, and locale fallbacksA practical setup for hreflang alternates, x-default, localized sitemaps, translated slugs, and locale fallback chains in a multilingual Next.js site.
- Translating a Next.js site with Gemini, without breaking productionHow to machine-translate MDX content with the Gemini Batch API at half the token price, validate every response before it is stored, and only pay for what actually changed.
- Why multilingual content belongs in gitHosted CMS databases and translation platforms give you three sources of truth that drift apart. Keeping English MDX, translations, and history in one repo fixes that. Here is the model behind Scribe.