Files
SluijsensandClaude Sonnet 5.5 288b0e3838
Continuous Integration / check (pull_request) Successful in 1m50s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 8m50s
Continuous Integration / deploy-production (pull_request) Skipped
Adds the AI-DLC documents of the CMS and API foundation feature
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-08 02:06:00 +01:00

4.4 KiB

Units of Work: cms-api-foundation

Three units. Terminology: a unit is a planning and build unit of one deployable system (the CMS host plus its admin) split into logical chunks; nothing here becomes an independently deployable service. Repository paths: CMS = K:\Development\Projects\SlpModularCms, WEB = this repo.

U1 core-site-hosting (CMS repo, built by the CMS session)

  • Purpose: Teach the shared host to serve a prerendered website the way nginx does today, and give such a site a strict CSP, without changing any existing host.
  • Components: C2 CmsHostOptions.WebsiteMode, C3 prerendered site serving (resolver, middleware, cache policy, indexing policy, compression), C4 StrictSite policy.
  • Requirements: FR-3, FR-8, FR-9, FR-10 (policy part), NFR-2, NFR-3, NFR-4, NFR-6 (resolver and policy tests), NFR-8 (CMS docs).
  • Construction stages: Functional Design, NFR Requirements, NFR Design, Infrastructure Design (only if the host change touches deployment; expected none), Code Generation.
  • Done when: unit and property-based tests pass; Api and Api.SlpSoftware behave unchanged (their tests green); WEBSITE_WORKSPACE.md and README describe the mode; the hand-back note is written. Checkpoint: the CMS session reports back after U1 before starting U2.
  • Code location: src/SlpModularCms.Core/Hosting (and .../Security) plus src/SlpModularCms.Core.Tests.

U2 andreaslop-client (CMS repo, built by the CMS session)

  • Purpose: Andrea's own host with a themed Dutch admin, deployed to test through the CMS CI/CD.
  • Components: C1 SlpModularCms.Api.AndreaSlopFotografie (project, appsettings, database, dev port, module references without Offerings, WebsiteMode = PrerenderedPages, SecurityHeaders and Website configuration), C5 admin theme themes/andreaslop/ and VITE_THEME/VITE_DEFAULT_LANGUAGE, C6 CMS CI/CD (per-client admin build, publish, deploy, wwwroot/web/ kept outside the swapped release).
  • Requirements: FR-1, FR-2, FR-4, FR-5, FR-6, FR-7, FR-10 (configuration part), FR-11, NFR-1 (setup flow exposure, logging), NFR-5, NFR-6 (client tests), NFR-7.
  • Construction stages: Functional Design (module minimum, setup flow), NFR Requirements, NFR Design, Infrastructure Design (database for the new host, ports, release layout, CI matrix), Code Generation.
  • Done when: the host starts on test with its own database, /admin shows Andrea's theme in Dutch and allows first-admin setup and login, /api/v1/System/capabilities lists no Offerings, /health is green, and Api.SlpSoftware still builds and deploys unchanged.
  • Code location: src/SlpModularCms.Api.AndreaSlopFotografie, frontend/themes/andreaslop, .gitea/workflows, solution placement under Clients per the CMS repo's AGENTS.md.

U3 site-delivery (WEB repo, built by this session)

  • Purpose: Get the prerendered site onto Andrea's host and prove it behaves like the old static deployment.
  • Components: C7 delivery job in the web CI, C8 extended web/deploy/verify-deployment.sh (exact CSP, canonical redirects, 404.html status, cache and noindex on test, admin and API reachable), retiring the static nginx test site after proof.
  • Requirements: FR-12, FR-13, FR-14, FR-10 (drift guard), NFR-2, NFR-3 (Lighthouse not lower), NFR-5.
  • Construction stages: Infrastructure Design, Code Generation. (Functional Design, NFR Requirements and NFR Design are skipped as planned.)
  • Done when: a web CI run on the target branch delivers the build to the test host; verification passes; the static test site is retired.
  • Code location: this repo's CI workflow and web/deploy/. No change to web/src. Starts after the Testimonials feature has merged or overlap is ruled out.

Cross-cutting

  • FR-15 (collaboration with the CMS session) spans all units. One brief covers U1 and U2 (owner decision); the CMS session sequences them and reports back after U1. The brief lives in this feature's folder and a copy is placed in the CMS repo's AIDLC folder.
  • Build and Test (phase level) covers the proof across all three units on test.
  • Operations (Deployment, Monitoring, Production Readiness) covers the new host on test.
  • Code organisation: brownfield; no new top-level directories in this repo. Documentation only under aidlc-docs/features/cms-api-foundation/; the CMS session records its approved design and hand-back under construction/cms-host/ here.