Julien Gautier cf2ff7b231
CI / commits (pull_request) Successful in 3m45s
CI / scan (pull_request) Successful in 3m58s
CI / check (pull_request) Successful in 4m11s
CI / a11y (pull_request) Successful in 2m14s
CI / perf (pull_request) Successful in 7m22s
chore(gitlab): add MR template (ADR-0028 phase 1)
Port .gitea/pull_request_template.md to .gitlab/merge_request_templates/
Default.md so new GitLab MRs surface the same structured prompt once
Phase 2 lands the pipeline and developers start opening MRs.

Two content adjustments vs the Gitea original:
- PR -> MR in the comment header (GitLab terminology).
- Fixed a stale ref to docs/development.md "section 5" (Observability
  dev-loop); the Conventional Commits convention is in section 7.

Phase 1 ships repo-side artefacts only; ops bootstrap (mirror push,
groups, branch protection, bot signing keys, Renovate endpoint
reconfig) happens on vm-gitlab outside this PR per ADR-0028
section 'Migration sequence'.
2026-05-26 16:42:04 +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%