Using the DXA BluePrint

The DXA installation process includes the option of importing sample Publications, which make up a simple, linear BluePrint. You can integrate these Publications in your existing BluePrint and reuse existing content, or you can create a new, separate BluePrint hierarchy.

The following screen`capture shows the DXA BluePrint Publications:

The basic BluePrint demonstrates the essentials of BluePrinting, namely the separation of content (Components and Pages) from content definition and design (Schemas & Templates), and also a single Publication for Publishing content to a website.

In reality, you will always have more complex requirements. The following sections describe scenarios for setting up a BluePrint depending on your implementation.

Multiple website BluePrint

To manage several websites (for example websites for different countries or different types of websites such as a product launch site, country site, partner portal, and so on), it is good practice is to set up a website master Publication for each website type and create your website Publications as Child Publications of the appropriate website master Publication so that any common content, pages or structure (for example, all country websites have a News section) are created at the master website level and shared to all children. For example:

Sharing content between multiple websites BluePrint

If you have content such as terms and conditions, privacy policy, general company information, and so on which is global to multiple sites, create a Publication for global content higher in the BluePrint. For example, create a Child Publication of the 100 Master Publication and make your website Publications (or your website master Publications) that use global content as children of this. Any content created in this Global Content Publication is then shared to all Child Publications (the content is reused and centrally managed). For example:

Multilingual website BluePrint

If you want to show the same content in different languages, localize the content Components and translate them. If you have different websites for each language, for example country websites, ensure that you use a master web Publication to share the content across all country websites. You can then localize the Components in the country website to translate it to the appropriate language.

The BluePrint is similar if you have a single website available in multiple languages, except that you might publish the master Web Publications as your 'primary' site language. For example:

If you have multiple websites which share the same language and content, create a translation layer for in the BluePrint. For example, create Child Publications of a Global Content Publication for each language. The translation layer should sit above any website definition, and each site should have a the appropriate translation Publication as a parent:

Other Scenarios

The examples above are intended as a start point and are by no means a full coverage of all blueprint options. If you have multiple site requirements, and wish to share and/or translate content between sites then it is a good idea to contact your SDL, or SDL partner representative to arrange a BluePrint workshop or training session.