Hi here. I'm a CMS Manager for an AU based company and we're trying to migrate our sites and create new sites in Umbraco. Sorry, but this will be long. Some notes: - Using Umbraco 11.4.2 - Only have an editor access (but was just granted an Admin). - Have no familiarity when it comes to setting up a new site from scratch. - 2 sites already in Umbraco - AU and rest of the world; only AU is live. https://au.blueberrymarkets.com/ and https://blueberrymarkets.com/ (not yet live, but site root + homepage is in Umbraco). Requirement - Our management would like to create a new site for CN, and other languages. We currently have one for Australia that was built in Umbraco 11 and went live last month. Questions- 1. I reached out to your HQ via email and in contact with Catalina, however, I need more information and recommendations. With the requirement above, on the developer side, would you recommend a to create a multisite setup or multilanguage instead? In terms of setting up, which is longer or more tedious? I only work as a Content Manager/Editor and have not set up a site from the start. 2. Our team also would like to install a package or translation plugin - The purpose of this in case is to translate the copy of the current AU (en) site to CN/Chinese and the copy will then be reviewed and edited as needed by a local team member . Is this possible and what would be the best translation package? Second, if we set up a multilanguage site instead, do we still need a translation package? Additional question also on this. I was looking at https://docs.umbraco.com/umbraco-cms/tutorials/multilanguage-setup. Does this mean that if there are edits or customization of the other language from the AU en site, we cannot do this? Thank you in advance.

Hi, Its likely that you want to go down the multi-lingual variant root (which is as the example shows, having all of the languages in one content tree). There are times when it can be better to have a language per tree, but really only if each language is going to have a lot of pages that are only for that language - you can still do this in the multi-language way its just a bit more confusing. When you setup the muli-language pages, you can decided what properties on a page 'vary by culture' that is are diffrent for each language. so that would be things like text and textboxes, etc,