I would like to hear from the community some help/adivce on the best way to solve a problem i have with an existing client. We have already developed a fairly large website for a client of ours based around the hospitality sector. They have now asked us to build them a sister site which is relatively smaller. They only want a single instance of Umbraco and therefore run and maitain the content through it. The problem is they would like to share content from the main site in the new sister site (different domain name). They dont want to have to maintain two copies of certain pages. Is there anyway of doing this sensibly???
Hi Richard When you need to share content across multiple sites in the same installation an approach could be to create a content repository in the content section... So your setup could look like this:
Site A - Page 1 - Subpage 1 - Page 2 - Page 3 - Etc.
Site B - Page 1 - Subpage 1 - Page 2 - Page 3 - Etc.
So in the content repository it's possible to create folders and content elements that can be shared across the different pages on the sites when selected using the multinode treepicker datatype for instance. This would probably require some changes in your current setup but this way the editor can create elements to be reused throughout the site. Hope this helps. /Jan
Shared content across multiple sites
hi all,
I would like to hear from the community some help/adivce on the best way to solve a problem i have with an existing client. We have already developed a fairly large website for a client of ours based around the hospitality sector. They have now asked us to build them a sister site which is relatively smaller. They only want a single instance of Umbraco and therefore run and maitain the content through it. The problem is they would like to share content from the main site in the new sister site (different domain name). They dont want to have to maintain two copies of certain pages. Is there anyway of doing this sensibly???
Thanks in advance
Richard
Hi Richard When you need to share content across multiple sites in the same installation an approach could be to create a content repository in the content section... So your setup could look like this:
Site A
- Page 1
- Subpage 1
- Page 2
- Page 3
- Etc.
Site B
- Page 1
- Subpage 1
- Page 2
- Page 3
- Etc.
Content repository
- Content folder
- Box 1
- Box 2
- Box 3
- Content folder
- Content folder
- More content
- Etc.
So in the content repository it's possible to create folders and content elements that can be shared across the different pages on the sites when selected using the multinode treepicker datatype for instance. This would probably require some changes in your current setup but this way the editor can create elements to be reused throughout the site. Hope this helps. /Jan
is working on a reply...