Add i18n / multilingual support for the website

[clay-good]

Note

Moved from issue #1065, originally opened by @nektobit on 2026-05-07. Continuing the conversation here in Discussions — the original issue thread (including any comments) stays available at #1065 for the record.

---

Problem

The OpenSpec website is currently available only in English.
This creates a barrier for developers and teams who are interested in the project but are not confident English speakers.

Since OpenSpec has the potential to attract an international community, multilingual support could significantly improve accessibility and adoption.

Proposal

Add internationalization (i18n) support to the website and allow switching between multiple languages.

Possible first languages:

• English (existing)
• Chinese
• Spanish
• Russian
• Portuguese
• Japanese

Benefits

• Makes OpenSpec more accessible worldwide
• Lowers the entry barrier for non-English-speaking developers
• Helps community growth
• Enables community-driven translations
• Improves onboarding for new users

Possible implementation ideas

• Use a standard i18n solution depending on the website stack
• Store translations in separate locale files
• Add a language switcher in the navbar/header
• Allow community contributions for translations

Additional note

Even partial translation support (landing page + docs navigation) would already make the project much more welcoming for international users.