Julien Gautier
22fd93a43a
Two related brand-asset cleanups bundled per request: portal-shell — header logo: - Replace `apf-small.png` (a 7.6 KB raster wrapped through sharp from the original PNG-in-SVG file) with `apf-logo.svg`, an actual vector 1024×1024 export (2.1 KB). Sharper at any density, smaller payload, no rasterisation artefacts when the header zooms. - `header.html` swaps the `<img src=…>` accordingly. - The wide-format `apf-portal.svg` stays in place for future surfaces (login splash, etc.). portal-admin — favicons + PWA manifest: - Mirror portal-shell's PR #84 setup. Copy the six favicon image assets (favicon.ico, favicon.svg, favicon-96x96.png, apple-touch-icon.png, web-app-manifest-{192,512}.png) into `apps/portal-admin/public/favicons/`. Single visual identity across the two apps. - Customise `site.webmanifest`: `name: "APF Portal Admin"`, `short_name: "Admin"`. PWA install banners and home-screen icons read the right app name when admin is installed standalone. Icon entries + theme-color + display stay identical to portal-shell. - Wire `<link>` tags in `apps/portal-admin/src/index.html` mirroring portal-shell's, plus `<meta name="theme-color">`. - Remove the now-obsolete top-level `apps/portal-admin/public/favicon.ico` (replaced by the entry under `favicons/`, referenced via `<link rel="shortcut icon">`). Verified: `nx run-many -t lint test build --projects=portal-shell, portal-admin` green; both `dist/.../browser/{en,fr}/favicons/` ship the seven expected files; admin manifest contains "APF Portal Admin"; admin `index.html` has the right `<link>` block.
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.