The string value assigned to this key will be the description of the blueprint as it appears directly below the blueprint's name/title in the Blueprints Menu.
The string value assigned to this key is the space key of the source space that will serve as the template for new spaces generated from this blueprint.
The array assigned to this key will comprise the names of all custom substitution fields that will be a part of this blueprint.
These are the fields blueprint users will be asked to provide values for whenever they create new spaces or pages from this blueprint.
Each field name listed here will map to a blueprint field object defined in the JSON file. The substitution field name as it occurs in this array will match the corresponding blueprint field object's id key, which will also match the substitution field name as it occurs in the blueprint source page (enclosed in double brackets: [[substitution-field-name]]).
Defines how new spaces generated from a space blueprint will be named.
The string value of this key will be the name of a new space generated via blueprint.
It is possible and indeed recommended to incorporate at least one custom substitution field into this key's value so that each new space created from this blueprint will have a unique name from the start, without requiring any extra input from the user who is creating the new space. (Built-in substitution fields, however, are not supported here.)
"spaceBlueprints" : [ ... { "name" : "Team Workspace", "description" : "Workspace for a department or project team", "blueprintSpaceKey" : "teamspacebp", "blueprintFields" : [ "team-name", "team-lead-name", "team-lead-email" ], "spaceName" : "[[team-name]] Workspace", "spaceKey" : "[[team-name]]WS", "spaceDescription" : "Projects, timelines, and resources for the [[team-name]] team", "access" : [ "Team" ] } ... ]
"spaceKey" : "string"
Key/value pair
Defines the space key for new spaces generated from a blueprint;
OR
Indicates the space that holds a page blueprint's source page.
When this key/value pair occurs in a space blueprint object, the string value will be the space key of any new spaces generated via blueprint.
As with the spaceName key, it is possible and indeed recommended to incorporate at least one substitution field into this key's value so that each new space created from this blueprint will have a unique key from the start. Otherwise, when blueprint users try to create new spaces from blueprint, they will be prompted to go back and manually enter a unique space key to avoid naming collisions.
When this key/value pair occurs in a page blueprint object, the string value will simply be the key of the space that is holding the blueprint source page.
Another way to think about it: The space indicated here is where we'll find the value of "pageTitle".
"spaceBlueprints" : [ ... { "name" : "Team Workspace", "description" : "Workspace for a department or project team", "blueprintSpaceKey" : "teamspacebp", "blueprintFields" : [ "team-name", "team-lead-name", "team-lead-email" ], "spaceName" : "[[team-name]] Workspace", "spaceKey" : "[[team-name]]WS", "spaceDescription" : "Projects, timelines, and resources for the [[team-name]] team", "access" : [ "Team" ] } ... ]
editable via the Space Tools Menu) for any new space generated from the blueprint.
It is possible to incorporate custom substitution fields into this key's value, should you wish to do that, although the use of built-in substitution fields is not supported.
