Template

Files

Danijel Martinek f77e6ea881 chore(template): clean-slate template snapshot from bb4a0c7

Curated, product-agnostic snapshot of the post-story-04 tree: demo
content deleted, auth-only reference feature, web-next shell, all gates
green. Product-specific docs, ADRs 027-029, PRDs/epics/archive, editor
library traces, and product naming are curated out; generic template
repairs (coverage provider devDeps, root test:coverage script, live
lint fixes, root-only release-please) are kept. See TEMPLATE.md for
provenance, curation list, and usage.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK

2026-07-12 20:40:54 +02:00

1.3 KiB

Raw Blame History

ADR-003: CMS Core + CMS Client Separation

Status: Accepted

Context

Payload CMS needs to integrate with clean architecture without creating circular dependencies.

Decision

Three packages: @repo/cms-core (config + collections), @repo/cms-client (standalone typed client), apps/cms (thin shell).

Rationale

cms-core is testable independently — collections are just config objects
cms-client is standalone (no internal imports) — prevents circular deps
apps/cms is almost empty — just boots Next.js with cms-core's config
Payload instance injected into cms-client, not imported — app startup code wires them

Circular Dependency Prevention

apps/cms → @repo/cms-core → @repo/core/application (hooks)
@repo/core/infrastructure → @repo/cms-client (standalone)

No cycles because cms-client never imports from cms-core or core.

Status: Partially superseded by v2 (2026-05-04)

v1 advocated @repo/cms-core as a single CMS package. v2 splits this into:

@repo/core-cms — composition only (assembles feature CMS schemas)
Each feature owns its own collections/globals under packages/<feature>/src/integrations/cms/

Rationale: vertical-feature ownership scales better; CMS schema lives with the business code that needs it. See ADR-006.

1.3 KiB Raw Blame History