Article
Running Astro Content Layer inside a monorepo
A practical structure for shared schema, filtered listings, and locale-specific publishing.
This sample post represents a translation pair that shares the same five-digit translationKey across Japanese and English.
Centralize content first
Store article files in packages/content, then filter listings, search, RSS, and sitemap output by both site and locale.
That keeps the English listing clean while allowing Japanese-only articles to exist without leaking into the wrong language feed.
Stable translation links
Each locale can keep its own slug, but translation lookup should still use translationKey.
That rule makes language switching, fallback handling, and future Cloudflare logic much easier to keep consistent.
