feat(web): add bilingual website and central account frontend
This commit is contained in:
commit
622f396364
20 changed files with 1315 additions and 0 deletions
23
docs/verification.md
Normal file
23
docs/verification.md
Normal file
|
|
@ -0,0 +1,23 @@
|
|||
# Verification
|
||||
|
||||
Verified locally on 24 October 2026:
|
||||
|
||||
- `npm test`: 7 Node tests passed, including exact catalog parity, authentication request options, malformed-session checks, avatar-origin validation and encoded preview-path traversal.
|
||||
- `npm run build`: static build completed; assets normalized to mode 0644, directories 0755.
|
||||
- `node --check src/app.js`: JavaScript syntax check passed.
|
||||
- `python3 tests/browser_qa.py`: passed with the workstation's existing Playwright and `/usr/bin/chromium`; no browser or dependency was installed by this project.
|
||||
|
||||
The optional browser script requires the loopback preview from `npm run dev` or `npm run preview`. It replaces API responses with test fixtures and refuses non-loopback origins. It checks:
|
||||
|
||||
- Keyboard-operated illustration tabs and theme selection.
|
||||
- Runtime RU/EN changes and layouts at 320, 390, 768 and 1440 pixels, including account views.
|
||||
- Enabled, disabled and unavailable GitHub sign-in; retry after session failure.
|
||||
- Profile values rendered as text, rejected unsafe avatar URLs and no script execution from hostile profile fixtures.
|
||||
- CSRF-header/Origin/POST sign-out and expired-session handling.
|
||||
- Browser storage contains only the UI language; no account tokens are persisted.
|
||||
|
||||
Screenshots were visually inspected at `/tmp/vnox-web-qa/desktop-hero.png`, `mobile-full.png`, `account-login-mobile.png` and `account-profile-desktop.png`. Screenshot profile data is explicitly a browser fixture, absent from production assets.
|
||||
|
||||
## Limits
|
||||
|
||||
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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue