Files

1.8 KiB

Unit dependencies: hero-module

Rows depend on columns (X = needs it built first; (c) = only a contract, no code dependency).

H1 H3 H2 H4 H5 H6 ASF golden files SLS input
H1 Image pipeline n/a
H3 Media store and serving X (addresses, options) n/a
H2 Hero module backend X X n/a (c) JSON shape
H4 Injection X n/a X (tests) (c) title lines
H5 Admin X (API) n/a
H6 Delivery X X X n/a
flowchart LR
    H1["H1 Image pipeline"] --> H3["H3 Media store<br/>and serving"]
    H1 --> H2["H2 Hero backend"]
    H3 --> H2
    H2 --> H4["H4 Injection"]
    H2 --> H5["H5 Admin"]
    H3 --> H5
    H4 --> T1(["First test deploy"])
    T1 --> H5
    H4 --> H6["H6 Delivery"]
    H5 --> H6
    classDef u fill:#FFA726,stroke:#E65100,color:#000;
    classDef m fill:#CE93D8,stroke:#6A1B9A,color:#000;
    class H1,H2,H3,H4,H5,H6 u;
    class T1 m;

Text alternative: H1 feeds H3 and H2; H3 feeds H2; H2 feeds H4 and H5; the first test deploy follows H4; H5 and H4 feed H6.

Shared resources and contracts

  • The Core data block contract (H4) changes how Offerings writes #cms-data: its golden files must stay green.
  • The public JSON shape (H2) is a contract with the ASF and SLS sessions; the golden files from ASF (13f78c4) drive H4.
  • The media address scheme (H1) is used by H2 (data), H3 (endpoint) and H4 (HTML).
  • One migration (H2); no change to existing tables.

Parallelism

H2 and H3 can be built in parallel after H1 by different sessions, but the work is done by one session in the order above; the ASF and SLS sessions work on their sides in parallel from the first test deploy.