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

12
docs/copy-guidelines.md Normal file
View file

@ -0,0 +1,12 @@
# Copy guidelines
Short notes for writing site text in Russian and English. Based on README and landing-page advice from The Turing Way, openSUSE and others, Maxim Ilyakhov's "Пиши, сокращай" (Glavred stop-words), and articles on typical machine-written copy.
- Say what the thing is and for whom in the first sentence. List real things (channels, DMs, roles, encrypted voice) instead of slogans.
- Write only what the code does today. Planned items go under "next", never in the main description.
- Cut hype and filler: no "revolutionary", "seamless", "ecosystem", "powerful", "unlock"; in Russian no "осуществлять", "является", "данный", "в рамках", "обеспечивает возможность".
- Avoid the "not X, but Y" construction, triplets for rhythm, and openers like "Let's take a look". One plain sentence beats two clever ones.
- Prefer verbs and short sentences. Do not translate word for word: write the Russian and English versions separately, each as a person would say it.
- Use a full stop, comma, colon or brackets. The long dash character is banned in all site text; `tests/copy.test.ts` greps sources, docs and the built bundle for it.
- Titles and og/meta text follow the same rule, for example "VNOX: voice and text chat on your own server".
- Every user-visible string lives in `src/i18n/ru.ts` and `en.ts`. Keys must match; a test checks it.

View file

@ -25,6 +25,6 @@ Local QA screenshots were visually inspected in `/tmp/vnox-web-qa/`. Any authent
These frontend tests do not authorize a real GitHub user, verify provider consent or exercise Hub database/session internals. A live end-to-end GitHub authorization requires the account owner to complete provider consent. The loopback preview intentionally has no backend. Production deployment and HTTPS/security-header checks belong to the site's operator and must preserve the Hub's OAuth callback and cookie configuration.
## Production verification — 24 October 2026
## Production verification: 24 October 2026
Published source commit `622f396364bb` to [central.loki-code.dev](https://central.loki-code.dev), static release `622f396364bb-9b77c9dbd02c`. Live Chromium checks passed for desktop landing, anonymous account/GitHub entry, mobile account layout, CSS MIME and JavaScript console. Hub readiness/info, logo assets and authentication endpoints remain available at the same origin. CSP uses self-hosted scripts/styles, no external fonts, same-origin API connections and a specific GitHub avatar image origin. OAuth callback query logging remains disabled. A real user's GitHub consent/code exchange remains a manual verification step.