Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Martin 273 posts 654 karma points
    Aug 09, 2018 @ 14:45
    Martin
    0

    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.

    • Content
      • Site One
        • Child Page
      • Site Two
        • Child Page

    Or is it best to create the multi-sites in the root of the project?

    • Site One
      • Child Page
    • Site Two
      • Child Page

    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

  • Jan Skovgaard 11144 posts 22747 karma points MVP 4x admin c-trib
    Aug 09, 2018 @ 17:44
    Jan Skovgaard
    1

    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

      • 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!

    /Jan

  • Martin 273 posts 654 karma points
    Aug 10, 2018 @ 10:25
    Martin
    0

    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?

    • Brand 1
      • Home - hostname
        • Child Page
    • Brand 2
      • Home - hostname
        • Child Page
      • Home (ES) - hostname
        • Child Page

    Thanks for your help Jan.

    Martin.

  • Jan Skovgaard 11144 posts 22747 karma points MVP 4x admin c-trib
    Aug 10, 2018 @ 11:35
    Jan Skovgaard
    0

    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

Please Sign in or register to post replies

Write your reply to:

Draft