Setting up a Blueprint Publication
A blueprint publication needs to be set up with all the publication
resources relevant to template design and configuration. A blueprint
usually contains widgets, data sources, templates, etc. It is not
recommended to deploy a blueprint, but use as a container of all the
templates required to render site publications. Once a blueprint is
set up properly, it can be used to manage as many site publications as
required. The blueprint should have the following dependencies as
demonstrated in misc/demo/demo-blueprint/pom.xml
:
The demo blueprint's POM file,
misc/demo/demo-blueprint/pom.xml
declares the
following dependencies:
<dependency> <groupId>com.escenic.widget-framework</groupId> <artifactId>widget-framework-blueprint</artifactId> <version>4.5.2-2</version> <type>pom</type> </dependency> <dependency> <groupId>com.escenic.widget-framework</groupId> <artifactId>widget-pack-blueprint</artifactId> <version>4.5.2-2</version> <type>pom</type> </dependency>
These dependencies ensure a blueprint has access to all the resources needed to support Content Studio's template design and configuration functionality. Presentation-related resources are not included. Since a blueprint is never deployed, resources required for presentation and rendering are not required.
In order for a blueprint to be used, it must be set as the active blueprint of a site publication. For instructions on how to do this, see Set Publication Blueprint.