Blueprint

A blueprint is a ready-made app starter: pages, data structure (collections + fields), automations, default content, and onboarding wiring, all set up together. The end user picks it from the marketplace, names their brand, and Vincia sets up everything from your template in one click. After install, the user owns and edits the build — your blueprint isn't running in the background.

Two sizes: a full app (standalone, with its own chrome and brand prompts) or a module that drops into an app the user already has.

What lives in a blueprint

• manifest.json — id, version, included widgets/workflows, scopes
• schema/ — collection definitions (per the schema spec)
• pages/ — page-tree JSON, one file per page
• workflows/ — pre-wired automations
• assets/ — branded images, fonts, presets

Tooling

vincia create blueprint my-app
vincia dev          # spin up a build instance against your blueprint
vincia test         # validate schema + page-tree + widget compatibility
vincia publish      # submit to the marketplace

What gets reviewed

• Schema is internally consistent (no dangling foreign keys)
• Every widget referenced in a page exists in the marketplace at install time
• Workflow nodes referenced exist; their input/output types check
• No bundled scopes the user didn't consent to