Julien Gautier
0808c0be68
Add a CDK-menu locale switcher (FR / EN) to the footer's right
cluster, next to the accessibility link. Trigger reads the active
locale from `<html lang>` (set per locale by the build) and shows
the native name plus a globe + chevron. Selecting another locale
rewrites the URL prefix (`/en/...` ↔ `/fr/...`) and triggers a hard
refresh so the right bundle boots — per ADR-0019.
Architecture mirrors the existing theme switcher:
- `@angular/cdk/menu` for the trigger + roving-focus menu + escape /
click-outside dismissal.
- `ViewEncapsulation.None` because the menu opens in an overlay
portal outside the component host; BEM-style class names keep the
global emissions contained.
- The trigger's `aria-label` is `$localize`-marked with a named
placeholder so screen readers announce the current language.
Locale display names ("Français", "English") are deliberately NOT
i18n-marked. Universal switcher convention: each language is always
shown in its own language, both in the trigger label and the menu
items — translating them would defeat the purpose. The
`<button>` for each menu entry carries `[attr.lang]="locale.code"`
so screen readers pronounce the name correctly.
v1 is SPA-only:
- No backend cookie, no `/api/preferences/locale` BFF route, no
smart `/` redirect — those land when the BFF is in place. Until
then the locale prefix in the URL is the source of truth; the
next visit naturally lands on the same locale's bundle.
- The switcher works against the production build (`/en/`, `/fr/`).
Under `nx serve` the dev server has no locale prefix, so clicking
the trigger lands on a non-existent path. Expected — dev mode
serves the source locale by design (ADR-0019).
Touch target: the trigger keeps a 28px visible height to fit the
40px footer, but extends to 44px via vertical padding — meets the
ADR-0016 AAA touch-target minimum without inflating the footer.
Add Globe to the icon registry (single new entry).
Documentation index
This is the entry point to all project documentation. It is maintained automatically: any addition, rename, or removal of a .md file under docs/ must be reflected here in the same change.
Conventions
- Documentation is written in English.
- One topic per file. Group related files into a folder when there are three or more.
- Cross-reference with relative links so they keep working in GitHub, IDEs, and exported sites.
- For architectural decisions, do not add them here — they belong in decisions/ as MADR 4.0.0 ADRs.
Sections
Daily development
- development.md — repo layout, prerequisites, initial setup, daily commands, observability dev-loop (Jaeger UI, log ↔ trace correlation), dependency updates (Renovate), conventional commit cycle. Day-to-day reference for working on the project.
Architecture
- architecture.md — cross-cutting Mermaid diagrams: C4 system context, C4 containers, Nx module boundaries, CI/CD pipeline. Single-decision diagrams (auth sequence, ERD, etc.) live inline in their ADR.
Onboarding & environment
Setup guides for new contributors:
- setup/01-wsl-terminal-setup.md — modern WSL terminal (Zsh + Powerlevel10k + CLI tools)
- setup/02-dev-web-stack.md — Node via nvm, pnpm via corepack, Docker
- setup/03-angular-nx-monorepo.md — Angular + Nx monorepo bootstrap
Operations & runbooks
Empty — to be populated when we deploy.
Security, performance, accessibility
Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.