Special BluePrint structures
Content that users create, modify or localize in Experience Manager does not need to be stored in the Publication associated with the Web site being edited. You can configure alternative Publications for your content to end up in.
When a user on the staging Web site uses Experience Manager to create or localize a Page or Component, then by default, the Page or Component is created or localized in the Publication that was published to create the staging Web site. However, this may not always be the Publication in which you want a Page or Component to be created or localized.
For example, you may have a BluePrint structure in which the lowest Publication in the tree, representing a bilingual Web site, combines content from two parent Publications, each representing a language. For example, a bilingual English-Japanese Web site would inherit from two parent Publications, one containing Japanese Components and another containing English Components.
In this case, you would want English Components to be created and localized in the parent English Publication, and Japanese Components in the parent Japanese Publication.
For similar reasons, you may want your content items to be published and unpublished using a different Publication than the one that directly corresponds to the editable Web site.
- When you create a Site using the Site Wizard, you can specify an alternative BluePrint location in the Wizard.
- In the slide-out navigation Settings screen, you can specify an alternative BluePrint location for Sites you already created previously.