Using Blueprints can save a significant amount of time and effort for content creators in cases where several similar spaces or pages must be produced. For example, imagine that for each of your company's products you want a Product Home page and three child pages each describing the product (e.g. a Requirements page, a Budget page, and a Schedule page). After creating these archetypical pages (the source blueprints) and then defining a few substitution fields, such as product name and product description, plus some configuration in the JSON File, you are then ready to start making copies. An editor can then create a new Product Page set from the Blueprint Menu, type the specific product's name and description, and bingo: all four pages will be created, ready to go! If using: Replace me with something to note about this concept that falls outside the scope of the Definition section; andAdd the tight-bottom class to the Definition block above to narrow the gap between the two blocks. | 
