Why not just use the built in language support and have on site with different language?

Or you can create a multisite solution where all sites can share media and all all built on the same source code so they will share css's

Multisite:
https://www.episerver.com/learn/tech/technical-resources/multi-site/

Language support:
https://www.episerver.com/learn/tech/technical-resources/globalization/

Well, although they share the same branding and styling like color scheme and logo, they might not be sharing the same contents and pages. We also cannot use the in-built language for the same reason, let's use Alloy HK as an example. The Alloy site in HK will be dual language EN and ZH, but this EN version is different with the EN in Australia, the contents are different too.

The only thing they will share is the styling and assets. This is why I'm wondering if we can clone an existing site and start working from there, it will save a lot of time. Or the way I'm approaching the problem is incorrect?

Hi Caleb, Henrik already answered the possible approaches.

If you want to limit the actual Episerver sites amount (less licenses) then you still can use the language feature (localization, localize the same site to multiple languages).

So for your example you would use en-HK (english in Hong Kong) and zh-HK (chinese in Hong Kong) as the languages. The language version of a site doesn't need to have the same content between language versions.

Besides the basic setup to a language branch: www.some-corporate-site.example (default language), www.some-corporate-site.example/en-HK/ and www.some-corporate-site.example/zh-HK/, www.some-corporate-site.example/en-AU/

You could map TLDs to a language like this:

• www.some-corporate-site.au (maps to en-AU language)
• www.some-corporate-site.hk (maps to en-HK)
  • china would be something like www.some-corporate-site.hk/zh-HK/
    • (to be honest, can't remember if the above would work as there is a language already mapped to 'HK' TLD)
  • or www.some-corporate-site.com/zh-HK/ (default domain)

Thank you for the proposal Antti. I might be going off-topic a little but its related to my second question, we also have sites not sitting within the CMS but they intend to share the same styling, design and assets like documents. I'm not really familiar with the Episerver Content Delivery API, can I utilize this to share my assets to the non CMS-managed sites so that they have the same consistent look and feel?

Caleb

For those cases we are starting to deploy the GUI parts as nuget or bower packages so they can be used in different kind of solutions.

It is pretty easy to set up the creation of nuget packages and it works pretty good