The approach in the mentioned article is certainly one way of doing it.
But if for instance the multiple sites should be have different language versions another approach could be to have a structure like this
DK
DK site
Child pages
EN
Site
Child item
This way you can also have multiple sites under each language for instance.
It could also be that you have a client, which manages multiple brands within the same Umbraco instance (We have such a client at my current company) - In our case the structure is a like this
Brand 1
Language (ES)
Site
Child page
Language (DK)
Site
Child page
Brand 2
Language (ES)
Site
Child page
Language (DK)
Site
Child page
Language (SE)
Site
Child page
I think it's a better approach to have a wrapper around the sites like in Maggy's example and the example I provided above since it can be used to setup some tabs used for "Settings" for instance, which is typically nicer for the editors as well as the developers rather than cluttering the home page node of the site with these extra tabs for instance.
I hope this makes sense? :)
Well that's at least my 2 cents about it - Hope it's useful to you!
Your second option is more inline with what I'm about to build. It's a brand that has multiple territories. All sites will have there own country code domain, and be in English just now.
In your second option would you use the "Brand" as your site wrapper?
Umbraco Cloud - Multisites
Hi all,
I'm about to set up my first multi-site instance in Umbraco on Umbraco Cloud. I've found a great blog post about doing this on standalone Umbraco :
https://skrift.io/articles/archive/using-one-umbraco-instance-to-host-multiple-sites/
Ive got a few questions / queries about the setup.
The blog post uses a page called "Content" as a parent to the child multi-sites. Is this a common pattern? E.g.
Or is it best to create the multi-sites in the root of the project?
With the last structure, will there be any issues with the first site being the root of the Umbraco project?
Is there any issue you think I should be aware of when creating multi-sites, specifically on Umbraco Cloud?
Thanks
Martin
Hi Martin
The approach in the mentioned article is certainly one way of doing it.
But if for instance the multiple sites should be have different language versions another approach could be to have a structure like this
DK
EN
This way you can also have multiple sites under each language for instance.
It could also be that you have a client, which manages multiple brands within the same Umbraco instance (We have such a client at my current company) - In our case the structure is a like this
I think it's a better approach to have a wrapper around the sites like in Maggy's example and the example I provided above since it can be used to setup some tabs used for "Settings" for instance, which is typically nicer for the editors as well as the developers rather than cluttering the home page node of the site with these extra tabs for instance.
I hope this makes sense? :)
Well that's at least my 2 cents about it - Hope it's useful to you!
/Jan
Hi Jan,
Thanks for your reply.
Your second option is more inline with what I'm about to build. It's a brand that has multiple territories. All sites will have there own country code domain, and be in English just now.
In your second option would you use the "Brand" as your site wrapper?
Thanks for your help Jan.
Martin.
Hi Martin
Happy that I was able to help and that my input made sense :)
And yes, in that example "Brand" would be the site wrapper where we can add some brand specific settings for instance.
/Jan
is working on a reply...