Julien Gautier 8cac0b4fc1
CI / commits (pull_request) Successful in 2m1s
CI / scan (pull_request) Successful in 2m21s
CI / check (pull_request) Successful in 2m29s
CI / a11y (pull_request) Successful in 2m52s
CI / perf (pull_request) Successful in 5m8s
fix(portal-shell): dark mode actually applies to component-scoped surfaces
Three component stylesheets carried `:where(.dark) &` rules to react
to the `<html>.dark` class. Angular's emulated CSS encapsulation
descends into `:where()` and rewrites its contents with the
`_ngcontent-XXX` scoping attribute — the produced selector then
demands that `<html>` (which carries `.dark`) also carry the scoping
attribute, which it doesn't, so the rules never matched.

Visible symptom: the main page background and a handful of inner
states (sidebar hover/focus/active, theme-switcher menu surface)
stayed light even when `.dark` was on `<html>` and every Tailwind
`dark:` utility in the templates was working correctly.

Fixes:

- `app.scss` and `sidebar.scss` switch to `:host-context(.dark)` for
  their dark variants. The Angular template compiler recognises
  `:host-context()` and expands it without forcing the ancestor to
  carry the scoping attribute.
- `theme-switcher` switches to `ViewEncapsulation.None`. Its CDK menu
  opens in an overlay portal outside the component's host, so even
  `:host-context()` would miss it. The styles ship globally; the
  BEM-style class names (`.theme-switcher__menu`, ...) are specific
  enough to keep the rules contained.

Drive-by:

- Remove the right border on the header logo zone — the visible
  vertical hairline above the sidebar was extra noise; the alignment
  of widths already carries the visual relationship to the rail below.
2026-05-11 10:12:57 +02:00

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:

Operations & runbooks

Empty — to be populated when we deploy.

Security, performance, accessibility

Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.

S
Description
No description provided
Readme 42 MiB
Languages
TypeScript 85.3%
JavaScript 5.4%
SCSS 4.3%
HTML 3.9%
Shell 0.8%
Other 0.3%