Set up campaign SiteAccess¶
The following example shows how to set up a special campaign
SiteAccess.
This SiteAccess serves a site devoted to a special campaign, separate from the main company website (site
SiteAccess).
The campaign
site uses a different part of the content tree than the main site, but shares some media files with it.
Configure SiteAccesses¶
First, in the SiteAccess configuration in config/packages/ezplatform.yaml
,
add the campaign
SiteAccess to the list under ezplatform.siteaccess
:
1 2 3 4 5 6 7 8 9 10 |
|
The match
setting ensures that when a visitor accesses the <yourdomain>/summer-sale
URI,
they see the campaign
SiteAccess.
Set root folder¶
Next, with the following content structure, you need to separate the "Campaign" folder as root for the new site:
To do it, set the root level for campaign
to access the "Campaign" Location and its sub-items only:
1 2 3 4 5 6 7 |
|
Thanks to this configuration, you can access <your site>/campaign/Articles/Article2
,
but not <your site>/campaign/General/Articles/Article1
.
Reuse content¶
Finally, reuse some content between sites, for example "Logos" from "Images/Media".
You can allow the campaign
site to access them, even though they are in a different part of the tree, via excluded_uri_prefixes
:
1 2 3 4 5 6 7 |
|
Now, when you use the campaign
SiteAccess, you can reach <your site>/campaign/Media/Images/Logos
,
despite the fact that it is not a sub-item of the "Campaign" Location.
As a next step, you can configure different designs for the two SiteAccesses.