Translation files: area files in place and the common texts for shared labels

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-15 17:36:38 +01:00
co-authored by Claude Sonnet 5.5
parent 246ebe5fd6
commit ab33e1fc83
13 changed files with 55 additions and 2 deletions
+6
View File
@@ -15,6 +15,12 @@ Not in the language files: the hero (becomes a CMS module), the privacy statemen
Dotted paths: the file name, then the page or section, then the element: `home.pricing.title`, `shoots.newborn.faq.0.question`, `common.aria.backToTop`, `common.form.errors.required`, `seo.pages.contact.title`. A list is an array in the JSON and keeps the order of the page; a position is a number in the path. Parameters are written `{name}`; a text with a plural has the forms `one` and `other` (`photos.one`, `photos.other`) and `{count}` is filled in by `tPlural`. No HTML in the texts: a text with a link or emphasis is a structured list of parts, as the content modules already have.
## Two ways to read a text
- A single text in a component: `t('home.pricing.title')`, or `tList(...)` for a list of plain texts, `tPlural(...)` for singular and plural.
- Structured content (a list of items with several texts, such as the questions and answers of a page): the content module reads the typed tree directly, `messages.shoots.newborn.faq.map((item) => ({ question: item.question, answer: item.answer }))`. A missing property breaks `tsc`, the same as a missing key. The content modules in `web/src/content` keep their types, images and paths and take the words from `messages`.
- `t()` is not given keys that are built at run time (`` `faq.${i}.question` ``): use the tree for lists.
## How a missing text is found
- `t('...')` only accepts keys that exist in the Dutch files; a typo or a missing key stops `tsc` and the build.
+10
View File
@@ -47,6 +47,16 @@ export default tseslint.config(
],
plugins: { react },
rules: {
// Text in attributes that people read or hear (labels, alt text)
'no-restricted-syntax': [
'warn',
{
selector:
"JSXAttribute[name.name=/^(aria-label|aria-description|alt|title|placeholder|label)$/][value.type='Literal']",
message:
'Put the text in a language file (src/i18n) and use t().',
},
],
'react/jsx-no-literals': [
'warn',
{
+21 -1
View File
@@ -1,4 +1,13 @@
import about from './nl/about.json';
import common from './nl/common.json';
import contact from './nl/contact.json';
import home from './nl/home.json';
import instagram from './nl/instagram.json';
import portfolio from './nl/portfolio.json';
import seo from './nl/seo.json';
import shoots from './nl/shoots.json';
import site from './nl/site.json';
import testimonials from './nl/testimonials.json';
// The texts of the site, per language, as JSON per area (src/i18n/<locale>/*.json).
// Only Dutch exists now. The types come from the Dutch files: a second language
@@ -9,7 +18,18 @@ import common from './nl/common.json';
// No library: the files are imported as modules, so prerendering, hydrating
// and the host injection all see the same text without a loading step.
export const nl = { common };
export const nl = {
common,
site,
home,
about,
contact,
shoots,
portfolio,
instagram,
testimonials,
seo,
};
export type Messages = typeof nl;
+1
View File
@@ -0,0 +1 @@
{}
+9 -1
View File
@@ -1,5 +1,13 @@
{
"aria": {
"backToTop": "Terug naar boven"
"backToTop": "Terug naar boven",
"skipToContent": "Direct naar de inhoud"
},
"site": {
"name": "Andrea Slop Fotografie"
},
"newTab": {
"short": "(opent in nieuw tabblad)",
"instagram": "(Instagram, opent in nieuw tabblad)"
}
}
+1
View File
@@ -0,0 +1 @@
{}
+1
View File
@@ -0,0 +1 @@
{}
+1
View File
@@ -0,0 +1 @@
{}
+1
View File
@@ -0,0 +1 @@
{}
+1
View File
@@ -0,0 +1 @@
{}
+1
View File
@@ -0,0 +1 @@
{}
+1
View File
@@ -0,0 +1 @@
{}
+1
View File
@@ -0,0 +1 @@
{}