Docs: frontmatter lang schema should match supported locales #143

New issue

Closed

opened 2026-04-20 03:21:23 +00:00 by pokebedrock-bot · 0 comments

pokebedrock-bot commented

2026-04-20 03:21:23 +00:00

(Migrated from github.com)

Summary

schemas/frontmatter.schema.json currently accepts lang values for fr, de, pt, it, and ja, even though this repository only ships docs/en/** and docs/es/** content and the build/search scripts only enumerate en/es as supported locales.

Evidence

Current schema enum includes: en, es, fr, de, pt, it, ja.
Current content tree only contains localized docs/snippets under docs/en/** and docs/es/**.
Local repro on main:
- Added a temporary docs/en/__tmp-invalid-lang.mdx with valid frontmatter except lang: fr.
- npm run lint:frontmatter:run still exited 0 and reported Validated 31 markdown files.

Impact

Contributors can accidentally stamp unsupported locale metadata onto pages and still pass CI. That makes the docs contract looser than the actual repository/build pipeline, and it increases the risk of stale or misleading localization metadata getting committed.

Acceptance criteria

Frontmatter validation rejects lang values outside the currently supported repo locales.
Contributor-facing docs clearly state which locale codes are currently valid in this repository.
npm run ci passes after the validator/docs update.

## Summary `schemas/frontmatter.schema.json` currently accepts `lang` values for `fr`, `de`, `pt`, `it`, and `ja`, even though this repository only ships `docs/en/**` and `docs/es/**` content and the build/search scripts only enumerate `en`/`es` as supported locales. ## Evidence - Current schema enum includes: `en`, `es`, `fr`, `de`, `pt`, `it`, `ja`. - Current content tree only contains localized docs/snippets under `docs/en/**` and `docs/es/**`. - Local repro on `main`: - Added a temporary `docs/en/__tmp-invalid-lang.mdx` with valid frontmatter except `lang: fr`. - `npm run lint:frontmatter:run` still exited 0 and reported `Validated 31 markdown files.` ## Impact Contributors can accidentally stamp unsupported locale metadata onto pages and still pass CI. That makes the docs contract looser than the actual repository/build pipeline, and it increases the risk of stale or misleading localization metadata getting committed. ## Acceptance criteria - Frontmatter validation rejects `lang` values outside the currently supported repo locales. - Contributor-facing docs clearly state which locale codes are currently valid in this repository. - `npm run ci` passes after the validator/docs update.