Multi-language and Multi-domain sites

Your Stacks site is built on a robust platform that allows for the setup of both multi-language and multi-domain sites. 

Multi-language

Using Stacks' multi-language features allow you to author content in multiple languages to ensure your user's/patron's inclusive access to your content. 

There are different options available to you when it comes to translating your site, you can: 

• Manually translate all content
• Use Google Translate for translating your content
• Or use a combination of both, manually translating some content while also using GTranslate to fill in any gaps

If needed, we can also dynamically change the path prefix (e.g., /es) or the domain (e.g., en.sitename.com) to identify the current site language as the user switches languages. This means multilingual sites can use domain-based language detection without requiring a multi-domain setup. 

Considerations

Before getting too far into setting up your Stacks site there are a couple of important items to note when it comes to languages.

1. Set your default language first!
   1. Once set, it is not recommended to change this, especially after you have started creating content
2. When manually creating content in multiple languages, you will need to ensure those languages are installed beforehand 

Multi-domain

Multi-domain is a setup ideal for managing multiple sites that are connected by shared content and/or settings. The versatility of multi-domain sites allows you to ensure continuity while also providing flexibility for each domain to be unique in appearance and content when needed. 

Considerations

When it comes to multi-domain sites, it is important to note some settings will be global across all domains, whereas others will be domain specific; here is a quick rundown of some of these settings:

• Users
  • When creating user accounts, you can specify which domain(s) the user will have access to
  • Single Sign On (SSO) via OpenAthens is supported for multi-domain sites. A released attribute is used to determine who has access to each domain
• Search
  • The primary search bar can be configured to have different searches enabled, but please note they will all use the same credentials (when applicable). The exception to this is with the EDS integration, which can support different profiles per domain
• Menus
  • Main menus can be configured per domain
• Content
  • When creating content, settings in the Publishing Workflow allow you to determine which domain(s) the content should be shared with
• Style Editor
  • The style editor is unique to each domain allowing administrators to configure the appearance of each domain as needed