Date: Thu, 28 Mar 2024 19:12:20 +0000 (UTC) Message-ID: <477293324.131.1711653140550@ip-10-0-1-24.us-west-2.compute.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_130_1710752138.1711653140547" ------=_Part_130_1710752138.1711653140547 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
How to create a blueprint at the space level.
Prerequisites
Before you begin building your space blueprint, you'll want to:
Similar to page blueprints= , space blueprints are templates from which copies are made. So the pro= cess for creating a space blueprint is rather like that of creating a page blueprint fo= r however many pages you want in your space. It is convenient to have these= pages packaged as a space blueprint because often a space needs to be able= to be replicated in a standardized way.
For example, on a company intranet, every department may need its own sp= ace, and yet every department shares at least some standardized (archetypic= al) pages, such as a home page, a team-member page, a mission statement pag= e, and schedule or calendar page. With a space blueprint, you can bundle fo= ur page blueprints together so that when a new team space is created all fo= ur of these pages are created as part of the new space.
Simply put: think about your need for a space blueprint, what pages are = needed, and then create each page inside this space. To tap the full p= ower and value of using blueprints, you can use substitution fields in the pages in your space b= lueprint.
See Accessing and Editing the JSON File for instructions on how to do= wnload the file.
The spaceBlueprint object defines some properties used to help guide use= rs when creating a space from this blueprint.
These properties include:
What's especially convenient about Space Blueprints is that you do not n= eed to define each individual page in the space as a pageBlueprint in the J= SON file. The spaceBlueprint object ensures that during the create space fr= om blueprint process each page from the space blueprint, including page tre= es, will be automatically created and rendered with the substitution field = values.
In the same JSON file, you must define each of the substitution fields; = again with helpful information for the users creating a space from this blu= eprint.
For each substitution field, you must define the:
ID (The unique ID for the field=E2=80=93that is, what is between the=
[[ ]]
brackets in your page blueprints)
Name (A human-readable name for the field)
Required (A toggle for whether the field is required)
Type (Defines the display length of the field)
Help Text (Additional text to assist the user in filling out the fie= ld - appears below the data-entry field in the creation process)
Placeholder (Default text inside the field)
See again Accessing and Editing the JSON File for how to upload the f= ile.
If using:
If using:
If using:
If using: