Use one verb per action in the English UI: sign in, sign out, create account

2026-08-05 00:34:05 +02:00
parent 46548ae758
commit 34b668d49f
7 changed files with 25 additions and 9 deletions
@@ -275,6 +275,11 @@ Same test before adding a row to a table or the file map — a clause, not a par
  `i18n/`. Operator/developer-facing text — boot errors, log messages, guard messages — stays English.
  A pure view-model builder takes an optional `t` defaulting to its own English, so a unit test reads
  in words; handlers pass `ctx.t`.
+- **One verb per action in the English UI: sign in, sign out, create account.** Not "log in",
+  "log out" or "sign up" — a second spelling for one button reads as a second thing. Guarded by
+  `src/i18n/load.test.ts` (a test file cannot live in `locales/`, which loads every `.ts` in it as a
+  catalog); the noun ("a sign-in error") is unaffected. A plugin's catalog
+  and every other locale follow the same one-verb-per-action rule in their own language.
 - Use well formed, standard compliant, rich URIs. Prefer state in the URL over POST:ing in for
  for example list pages with filters and pagination. Do: "ids=x&ids=y" and not "ids[]=x&ids[]=y"
  and not "ids=x,y".