Feature Suggestion: Add Localization (i18n) Support to Keystatic CMS

[Jafar-Sabaouni]

Hi Keystatic team,

I’ve been experimenting with Keystatic CMS for a multi-language project, and while I love its simplicity and flexibility, I ran into significant challenges when trying to implement localization. I tried using Keystatic as-is for this purpose and explored a few workarounds (e.g., duplicating collections or tweaking file structures), but they were either sketchy or required too much manual effort. After investing a considerable amount of time, I realized that native support for internationalization (i18n) would make Keystatic far more powerful for users like me who need multi-language content.

Idea:

I’d like to suggest adding built-in localization support to Keystatic CMS. This could be implemented by:

• Introducing a localization option in the Keystatic config to define supported languages ( en, es, nl, fr).
• Adding a language toggle or field per collection or singleton, allowing content to be authored in multiple languages.
• Storing localized files in a structured way, such as content/blog/firstblog/en.mdoc, content/blog/firstblog/nl.mdoc, etc.,.

Benefits:

Streamlines multi-language content creation without forcing users to rely on sketchy workarounds.
Makes Keystatic more accessible for global projects.
Aligns with modern CMS expectations where localization is increasingly standard.