Here's what you need to know about building Space Blueprints.
The first array in the .json file relates to space blueprints. Within each object, you define key/value pairs that help users generate a space from a template. In the image below, one object exists in the
The following table describes keys that you define in a
spaceBlueprints object. If you prefer to omit space templates from your Blueprints wizard, leave the values for each key empty.
|a name for the Blueprint template; appears in the Blueprints wizard when a user clicks the Blueprints button|
|a description for the Blueprint template; appears in the Blueprints wizard when a user click the Blueprints button|
|the space from which to copy content and settings into the new space|
|a list of fields to show in the Blueprints wizard; values in these fields can act as substitutions in subsequent fields|
|a name for the new space; use substitution fields where appropriate|
|a key for the new space; use substitution fields where appropriate|
|one or more words used to categorize the new space; added as space labels|
|a description for the new space; use substitution fields where appropriate|
|a permission scheme for the new space|
Once you upload your .json definitions to Confluence, the Space Blueprints section in the Blueprint Definitions screen appears as such.
The following images show how the .json file maps to the Blueprints wizard.
The Copy Current Space option will only be visible if the user has Space Administrator permission or Space Export permission.
Still need help?