Blueprints import and export

What is a blueprint?

Blueprints are JSON packages describing reusable CMS structure: content types, fields, taxonomies, menus, settings, optional pages, sample entries, and media seed images. Validated against cms_blueprint_version 1.0.

Storage location

Example files live under storage/blueprints/—blog, review-site, products-apps, agency-business, and others.

Import workflow

1. Go to Tools → Blueprints (or Import / Export).
2. Select a blueprint package.
3. Review the summary—types, taxonomies, plugins required.
4. Enable Import entries for sample posts, products, or pages.
5. Run import on staging first; back up production before applying.
6. Resolve slug conflicts with existing content types.

What blueprints can include

• content_types — Required array (use [] for pages-only packages)
• taxonomies — Categories, tags, with terms
• settings — String key/value pairs merged into cms_settings
• pages — Static pages inserted before menus
• content_entries — Sample entries with taxonomy assignments
• media_seed — Unsplash images downloaded into media library on apply
• required_plugin_slugs — Plugins that must be active

Public URLs after import

Types with has_public_route get /{typeSlug} index and /{typeSlug}/{entrySlug} singles. Taxonomy archives use /{typeSlug}/{taxonomySlug}/{termSlug}.

Blueprints vs config sync

Troubleshooting

• Import validation error — Check slug format ^[a-z0-9][a-z0-9\-]{0,62}$; fields must be a list not a map.
• Missing images — media_seed only allows images.unsplash.com HTTPS URLs.