SDL Digital Experience Accelerator BluePrint
When you install DXA, a simple linear BluePrint is created consisting of five Publications. You can integrate the Publications in your existing BluePrint and reuse your existing content, or you can create a new separate BluePrint hierarchy.
The following screenshot 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 Web site.
In reality, you will always have more complex requirements. The following sections describe scenarios for setting up a BluePrint depending on your implementation.
- Multiple Web site BluePrint
- To manage several Web sites (for example Web sites for different countries or different types of Web sites such as a product launch site, country site, partner portal, and so on), it is good practice is to set up a Web site master Publication for each Web site type and create your Web site Publications as Child Publications of the appropriate Web site master Publication so that any common content, pages or structure (for example, all country Web sites have a News section) are created at the master Web site level and shared to all children. For example:
- Sharing content between multiple Web sites 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 Web site Publications (or your Web site master Publications) which 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 Web site BluePrint
- If you want to show the same content in different languages, localize the content Components and translate them. If you have different Web sites for each language, for example country Web sites, ensure that you use a master Web Publication to share the content across all country Web sites. You can then localize the Components in the country Web site to translate it to the appropriate language.
- 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.