Files
AndreaSlopFotografie/aidlc-docs/features/cms-api-foundation/inception/application-design/component-dependency.md
T
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

3.5 KiB

Component Dependencies: cms-api-foundation

Dependency matrix

Rows depend on columns ("x" = depends on).

C1 host C2 options C3 site serving C4 StrictSite C5 theme C6 CMS CI C7 delivery C8 verify
C1 Api.AndreaSlopFotografie x x (via CmsHost) x (config)
C2 CmsHostOptions
C3 Site serving x
C4 StrictSite
C5 Theme
C6 CMS CI x x
C7 Site delivery x (target) x (host exists)
C8 Verify x (live) x (behaviour) x (behaviour) x

Dependency diagram

flowchart LR
    C2["C2 CmsHostOptions"]
    C3["C3 Prerendered site serving"]
    C4["C4 StrictSite policy"]
    C1["C1 Api.AndreaSlopFotografie"]
    C5["C5 Admin theme"]
    C6["C6 CMS CI"]
    C7["C7 Site delivery (web repo)"]
    C8["C8 Deployment verification (web repo)"]
    C3 --> C2
    C1 --> C2
    C1 --> C3
    C1 --> C4
    C6 --> C1
    C6 --> C5
    C7 --> C6
    C8 --> C7
    C8 -. checks .-> C3
    C8 -. checks .-> C4
    classDef cms fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000;
    classDef web fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000;
    classDef newc fill:#f6e05e,stroke:#c05621,stroke-width:1px,color:#000;
    class C2,C3,C4,C5,C6 cms;
    class C7,C8 web;
    class C1 newc;

Text alternative: The new client host depends on the options, site serving and the StrictSite policy; the CMS CI builds the host and theme; the web repo's delivery depends on the CMS CI having deployed the host; verification checks the live behaviour of serving and policy. Blue = CMS repo, green = web repo, yellow = new client host.

Communication patterns

  • Compile time: the client project references Core and its modules (this is also what selects the modules). CmsHostOptions is passed in code.
  • Configuration: SecurityHeaders and Website sections per environment (appsettings; no secrets).
  • Build time: the admin reads VITE_* variables; nothing about the theme reaches the API.
  • Deploy time: the CMS CI delivers the release; the web CI delivers site files into wwwroot/web/. The two never write into each other's directories.
  • Runtime: the browser calls the host same-origin for everything (site, /admin, /api/v1); no CORS for the site.

Data flow: a request for a site page

flowchart TD
    R["Browser request /over-mij"]
    H["Security headers (StrictSite)"]
    RES["PrerenderedPathResolver"]
    F["Serve over-mij.html"]
    RD["301 to canonical path"]
    NF["404.html, status 404"]
    R --> H --> RES
    RES -->|file found| F
    RES -->|non-canonical form| RD
    RES -->|unknown| NF
    classDef step fill:#63b3ed,stroke:#2b6cb0,stroke-width:1px,color:#000;
    classDef ok fill:#9ae6b4,stroke:#2f855a,stroke-width:1px,color:#000;
    classDef bad fill:#fc8181,stroke:#c53030,stroke-width:1px,color:#000;
    class R,H,RES step;
    class F,RD ok;
    class NF bad;

Text alternative: A page request gets the security headers, then the path resolver decides between serving the page file, redirecting to the canonical URL or returning the 404 page with status 404.

Cross-session dependencies

  • C7 and C8 changes in web/deploy and CI are the only web-repo changes; they start after the Testimonials feature has merged or overlap is ruled out.
  • C1 to C6 are built by the CMS session; their approved design and hand-back are recorded in construction/cms-host/.