Template apply as add-a-site: copy content, derive dirs, pin deps

SPEC-109 §2–§3 + SPEC-110 §4 (kind: "site") — installing a full-site template adds a site: write the manifest's site SiteConfig, derive the content/sandbox destinations, scaffold-copy the package's trees, and pin the derived deps. This is the heart of the template mechanism.

changeset-release/main View source

Criteria completion

Tracking started Jun 24 — check back for trends.

Relationships

ID:SPEC-109Status:accepted

Site template packages, manifest, and scaffolding

ID:SPEC-110Status:accepted

Theme and template install robustness

ID:SPEC-115Status:accepted

Project asset resolution — the asset: scheme

ID:WORK-446Status:done

Multi-site --site targeting and config read/write helpers

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-445Status:done

Shared install resolver: tarball name, registry passthrough, source-type detection

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-451Status:done

Template package format and template.json manifest type

Priority:highComplexity:moderateMilestone:v0.25.0

ID:WORK-454Status:done

Template asset seeding and bundled sandboxes

Priority:mediumComplexity:moderateMilestone:v0.25.0

ID:WORK-455Status:done

Reference template fixture and scaffold-build CI

Priority:mediumComplexity:moderateMilestone:v0.25.0

changeset-release/main current done

main done claude/v0.25.0-impl-3 done claude/v0.25.0-workitems ready

Jun 24, 07:10 PM2264093
Created (done)by github-actions[bot]
Jun 24, 08:44 AMc4ba0af
Content editedby Claude
feat(create-refrakt): site templates — framework×purpose axis, apply, re
Jun 23, 07:22 PMa6bdcba
Content editedby Claude
plan(v0.25.0): accept specs/ADRs and decompose into 21 work items

Acceptance Criteria

Template apply writes the manifest's site SiteConfig into sites.<key> (sites.default/singular for a new project, sites.<name> for a multi-site add), deep-merged per SPEC-115
Content/sandbox destinations are derived from (framework starter layout) × (target site key); the package's content//sandboxes/ are copied in; the resolved contentDir/sandbox.dir are written into the SiteConfig
Deps are derived from site.plugins + site.theme.package and pinned as live dependencies; content is scaffold-copied (author-owned)
Full-site templates seed a new project or new site only (no overlay onto an existing site — the deferred section case)
--site names a new site; collision with an existing site errors (WORK-446)

Approach

Implement the kind: "site" apply branch over the shared resolver (WORK-445) and the multi-site helpers (WORK-446), using the template.json type (WORK-451). Greenfield runs through create-refrakt; add-a-site runs through the install surface — both share this apply.

Dependencies

WORK-451 — template.json type
WORK-445 — shared resolver
WORK-446 — multi-site --site + config helpers

References

SPEC-109 §2, §3; SPEC-110 §4

Resolution

Completed: 2026-06-24

Branch: claude/v0.25.0-impl-3. applyTemplate (scaffold.ts) composes a site template onto the framework starter: copies the template's content/ into the starter's content dir (the install-derived destination), merges the manifest's site SiteConfig (theme/plugins/routeRules/entityRoutes/assets/backgrounds) into refrakt.config.json, and pins derived deps (site.plugins + site.theme.package) — @refrakt-md/* at the refrakt version, others at latest. Content is scaffold-copied (author-owned). Full-site only (rejects kind:"section"). The new-site --site collision mechanism lives in install.ts (resolveTargetSite('new'), WORK-446, tested). 7 apply-template tests pass.

Note

The greenfield create-refrakt path is complete. The refrakt CLI install-time "add a template as a new site to an existing project" reuses the same resolver + helpers and is tracked under WORK-461.