Blueprints

Blueprints are part of Ultivo Toolkit Pro. In the free version the tab is visible but locked. See pricing.

A blueprint packages your project structure so you can reuse it on another WordPress install. Content, media and form entries are never included: a blueprint carries the shape of a site, not what has been typed into it.

What goes in#

Ultivo Toolkit → Blueprints lists everything that can be packaged, grouped by type, each with its key next to it so you can tell two similarly named items apart:

• Field groups
• Post types
• Taxonomies
• Options pages
• Forms

Tick the parts you want, or use All on a group to take everything in it. The panel on the right keeps count of what you have selected.

Naming and downloading#

A blueprint gets a name, a version and an optional description. The version is yours to manage: a blueprint you hand to a colleague, or reuse in six months, is easier to place when it says which iteration it is.

Download blueprint produces a .ultb file. Keep it with the project, commit it, or pass it to whoever sets up the next site.

Importing#

On the receiving site, upload the .ultb file under Import blueprint. Before anything is written, the screen shows exactly what the file contains and what already exists on the site, so an import never surprises you with an overwrite you did not intend.

Blueprints or Local JSON?#

They solve different problems, and they work together.

Local JSON syncs field groups to your theme continuously, so field changes travel with your code through version control. It is for one project, over time.

A blueprint is a deliberate snapshot you carry to a different project, and it covers more than field groups: post types, taxonomies, options pages and forms come along. It is for starting the next site with the setup you already got right on the last one.