Taalbestanden: één nl.json per site (blokken common, site, home, era), docs bijgewerkt; prerender-basislijn gelijk

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-15 21:17:43 +01:00
co-authored by Claude Sonnet 5.5
parent 2f614151df
commit c0e1393816
7 changed files with 206 additions and 207 deletions
+2 -2
View File
@@ -4,7 +4,7 @@ The static texts of the site live in language files, not in the components. Dutc
## Where things are
- `src/i18n/nl/*.json`: the Dutch texts, one file per namespace. The files are the source of the types.
- `src/i18n/nl.json`: the Dutch texts, ONE file per language with a block per area (below). The file is the source of the types. A second language is a second file (`en.json`) with exactly the same keys.
- `src/i18n/index.ts`: `t(key, params?)`, `tList(key)` and the `TextKey` type.
- `src/i18n/i18n.test.ts`: tests for the helpers and the language files.
@@ -17,7 +17,7 @@ The static texts of the site live in language files, not in the components. Dutc
| `home` | The texts of the landing page sections (about, packages intro, contact form, and so on). |
| `era` | The texts of the 2026 era variant of the landing page. |
(Target layout. The files were called `shared` and `landing` before; if you find those names in older notes, `common` and `site`/`home` replace them.)
(The blocks were called `shared` and `landing` earlier, and were separate files; `common` and `site`/`home` replace them, all in one `nl.json`.)
## Keys and placeholders