Ready-made collection

A ready-made collection is a "tenant-ready" example bundle — a design template + a starter schema + seeded data + a content-stub set, packaged so a tenant can install one collection and immediately have a running site they only need to customize.

What you ship

my-collection/
├── manifest.json
├── template/                       # the design template (Goal 14 contract)
├── schema/
│   └── domain.sql                  # additive table + index seeds
├── content/
│   ├── pages.json                  # filled-in page copy
│   ├── products.json               # demo product/service rows
│   └── images-manifest.json        # canonical demo-image references
├── preview/
│   ├── home-live.png               # live-rendered preview, not a mockup
│   └── product-page.png
└── README.md

Key contracts

• Composed over invented. Collections compose your template + schema + seed data — no new widgets or capabilities.
• Seed schema is additive. No table renames, no destructive ALTERs; only new tables + columns + indexes.
• Realistic seed data. Demo rows should be plausible (real restaurant names use placeholders that read as real; demo prices in the right ballpark).

Scaffold

vincia create ready-made-collection my-collection
cd my-collection
vincia preview
vincia publish --dry-run

Approval gates

1. Template valid — runs the design-template gate inline. 2. Schema additive only — gate fails on DROP / RENAME statements. 3. Live previews — preview images are runtime-rendered, not raster mockups.

Where to learn more

• /types/designer — sibling designer tiers.
• /docs/tier-guides/design-template — the template tier this collection composes.