Julien Gautier
a9b36efb75
First step of the admin track. Scaffold the second Angular SPA in
the workspace alongside `portal-shell`, with the architectural
decisions from the v1 ADRs already wired so subsequent feature PRs
can drop straight into modules.
What lands:
- App generated via `nx g @nx/angular:application` (with the
matching e2e project skeleton). Standalone, zoneless-ready,
prefix `app`, scss component styles, css root stylesheet, no SSR.
- Tags `scope:portal-admin, type:app` so module-boundary lint
treats `portal-admin` distinctly from `portal-shell` and only
allows it to depend on `scope:portal-admin` + `scope:shared`
libs.
- Tailwind v4 wired (`.postcssrc.json` + `@import 'tailwindcss'`),
class-based dark mode (`@custom-variant dark ...`), brand palette
imported from `libs/shared/tokens/src/brand-tokens.css` —
identical visual baseline to portal-shell. ADR-0016 a11y baseline
applies; ADR-0017 perf budget relaxed to **500 KB gzip initial**
per ADR-0020 §"Performance budgets".
- i18n configured to mirror portal-shell (per ADR-0019): sourceLocale
`en`, target `fr`, baseHref `/{locale}/` per locale,
`@angular/localize/init` polyfill, `localize: ["en", "fr"]` on
production, `i18nMissingTranslation: "error"` so CI blocks any PR
that adds a marker without translating it. Seed `messages.fr.xlf`
carries the four marked strings used by the placeholder page +
skip-link + route title.
- Skeleton home page at `/` with a placeholder `<h1>`, intro
paragraph, and a small "Skeleton — coming soon" status chip in
the brand-accent palette. Marked for i18n.
- Skip-link landmark (WCAG 2.4.1) at the App level, with the same
styling as portal-shell (component-scoped scss).
- Wildcard catch-all route bounces unknown paths to home, same
defensive pattern as PR #96 on portal-shell.
- Dev server on port **4300** (vs 4200 for portal-shell) so both
can run in parallel during cross-app development.
- `serve-static` target without `spa: true` — locale-prefixed
routing in production will be handled by the reverse proxy (per
ADR-0019), same as portal-shell since PR #92.
Production build: 62 KB gzip initial per locale (vs the 500 KB
relaxed budget). Both `dist/apps/portal-admin/browser/{en,fr}/`
emitted with the right `<html lang>` and `<base href>`.
Out of scope (each its own follow-up PR):
- Admin app shell (header / sidebar / footer with "Admin" badge).
- OpenTelemetry tracing setup (will register as
`service.name=portal-admin` per ADR-0012).
- `environment.ts` wiring (per ADR-0018) for the admin's own BFF
endpoints.
- BFF `AdminModule` + `AdminRoleGuard` + first `/api/admin/me`
smoke route (per ADR-0020 §"Auth").
- First functional module (CMS / menu / users / audit viewer).
CLAUDE.md picks up the second app in its naming + commands sections.
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.