2.4 KiB
2.4 KiB
Unit of Work Plan: cms-api-foundation
Terminology: the CMS side is a set of modules of one deployable host; "unit of work" is a planning unit, not a deployable service. No user stories exist (skipped), so the story map maps requirements (FR/NFR) to units.
Proposed decomposition
The execution plan named two units (U1 CMS host, U2 site delivery). The application design suggests a split of the CMS side, because the shared-host change (Core) is critical and must not regress Api.SlpSoftware, while the client project, theme and CI are new and isolated.
| Unit | Repo | Contents | Built by |
|---|---|---|---|
U1 core-site-hosting |
CMS | C2 CmsHostOptions, C3 prerendered site serving, C4 StrictSite, tests, CMS docs (WEBSITE_WORKSPACE.md, README) |
CMS session |
U2 andreaslop-client |
CMS | C1 Api.AndreaSlopFotografie, C5 admin theme and default language, C6 CMS CI/CD for the new host |
CMS session |
U3 site-delivery |
WEB (this repo) | C7 delivery job, C8 extended verify-deployment.sh, retiring the static test site |
This session |
Order: U1, then U2, then U3. U3 starts after the Testimonials feature has merged or overlap is ruled out.
Plan
- Analyze requirements and application design
- Collect answers to the questions below
- Generate
application-design/unit-of-work.md - Generate
application-design/unit-of-work-dependency.md - Generate
application-design/unit-of-work-story-map.md(requirements to units) - Validate unit boundaries and dependencies; ensure every FR/NFR belongs to a unit
Questions
Question 1: Splitting the CMS side
- A) Two units on the CMS side (U1 shared host, U2 Andrea's client), as in the table. Recommended: U1 has its own checkpoint (SlpSoftware regression, unit tests green) before the new client is built on it.
- B) One CMS unit covering both.
- X) Other (describe after the Answer: tag below)
Answer: A (two CMS units). Owner: the client project is named Api.AndreaSlopFotografie instead of Api.AndreaSlop.
Question 2: Briefs to the CMS session
- A) One brief per CMS unit (U1, then U2 when U1 is hand-backed). Recommended: matches "one feature at a time" for the CMS session's AIDLC.
- B) One brief for both CMS units; the CMS session sequences them itself.
- X) Other (describe after the Answer: tag below)