feat(web): rewrite site copy in plain language and split i18n dictionaries

Move RU/EN strings to src/i18n/{ru,en}.ts, add og/meta tags that follow the
selected language, remove the long dash from all text, add copy guidelines and
tests for key parity, HTML fallback text and dash-free sources and bundle.
This commit is contained in:
Loki 2026-10-24 16:55:05 +02:00
parent 0d80ca9433
commit d3a6dd316b
Signed by: boba
GPG key ID: 253067914055423B
11 changed files with 397 additions and 295 deletions

View file

@ -1,4 +1,4 @@
# VNOX — Web
# VNOX Web
> Public project website and account frontend for VNOX Central.
@ -65,7 +65,7 @@ Optional browser QA: `python3 tests/browser_qa.py` uses an existing local Playwr
```text
public/ HTML entry point and self-hosted assets
src/ Typed application, API helpers, RU/EN catalogs and CSS
src/ Typed application, API helpers, CSS; src/i18n/ holds the ru.ts and en.ts string dictionaries
scripts/ Bun browser bundling, static build and loopback preview
tests/ Bun regression tests and optional browser QA
docs/ Design, deployment notes and repository-hosted screenshots
@ -86,7 +86,7 @@ The Hub sets Secure, HttpOnly cookies. Tokens are never stored in browser storag
## Contributing
Keep RU/EN catalog keys aligned, render profile values as text and retain keyboard navigation and reduced-motion support. Use descriptive Conventional Commits such as `fix(web): preserve account state when changing language`. Run type checks, tests, formatting checks and a production build before submitting a focused PR; include screenshots for visual changes. See [verification notes](docs/verification.md) for browser QA and current limits.
Keep RU/EN catalog keys aligned (`src/i18n/ru.ts` and `en.ts`; a test enforces it), follow the [copy guidelines](docs/copy-guidelines.md), never use the long dash character, render profile values as text and retain keyboard navigation and reduced-motion support. Use descriptive Conventional Commits such as `fix(web): preserve account state when changing language`. Run type checks, tests, formatting checks and a production build before submitting a focused PR; include screenshots for visual changes. See [verification notes](docs/verification.md) for browser QA and current limits.
## License