Answers.Body: <p><strong>Edit</strong>: After the screenshot above was added in an edit, I realise that this question might have more to with how multi-site entries are managed in the control panel, and less with how the content itself is modelled, or how it's exposed on the front end.</p>
  <p>The short answer is that, no – there is no side-by-side or equivalent view for multi-site content in Craft, that is equivalent to the One-Tree TYPO3 view pictured above.</p>
  <p>In Craft, propagated multi-site entries can be switched between via the site dropdown in the top left corner of element edit pages and indexes.</p>
  <p><strong>Original answer</strong> <em>(doesn't really answer this particular question, but the info might still be useful to someone coming to Craft from TYPO3):</em></p>
  <p>I'm not familiar with TYPO3, but based on your description I'd say the closest equivalent to the One-Tree/Multiple-Tree concepts in Craft lingo is the term &quot;propagation method&quot; – i.e. in multi-site Craft installs, content can be configured to <em>propagate</em> across different sites, in different ways (or not at all).</p>
  <p>Sections (and Matrix fields) can be configured to propagate (or not) using mutiple different propagation methods. For example, you might have a section where all entries are propagated to all sites, another section that only propagates its entries to sites in the same site group, and even a section that doesn't propagate at all (i.e. equivalent to &quot;Multiple-Tree&quot;), etc.</p>
  <p>It's even possible to configure a section to let content authors <em>optionally</em> propagate specific entries to different sites, i.e. letting the content author decide if a particular entry should be available in multiple sites or not.</p>
  <p>Essentially, this means that in Craft, you can combine the One-Tree and Multiple-Tree approaches to multi-lingual content, and use one or the other (or combinations of the two), when and where it makes sense to any particular piece of content.</p>
  <p>Regardless of your approach to multi-lingual content modelling, the strategy for switching languages in the front end is completely up to you. To that end, it's completely possible to build a language switcher component that conditionally redirects the user to the same entry in the chosen language, or to the selected site/language's base/homepage URL if the current entry doesn't exist in that site/language.</p>
  <p>Here's <a href="https://craftsnippets.com/articles/universal-language-switcher-for-craft-cms?s=s" rel="nofollow noreferrer">an example</a> for such a language/site switcher component.</p>
  <p>Additionally, plugins like <a href="https://plugins.craftcms.com/geomate?craft5" rel="nofollow noreferrer">GeoMate</a> can be helpful in building language switchers (check out the <a href="https://github.com/vaersaagod/geomate/blob/master/README.md#craftgeomategetsitelinks" rel="nofollow noreferrer"><code>craft.geomate.getSiteLinks()</code></a> method).</p>
  <p>I'd also recommend reading the <a href="https://craftcms.com/docs/5.x/system/sites.html" rel="nofollow noreferrer">&quot;Sites &amp; Localization&quot;</a> guide in the official Craft docs, for a good overview on how multi-lingual content is approached in Craft.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-04-30T13:32:24.163Z
Answers.Text: Hi Mats, thank you for your long and detailed answer ... this is very helpful to me!  
  
  Now I have an idea how to work with this topic, what possible within the control panel an what not.  
  
  Every single CMS has its pros and cons. This view in my screenshot is a strong feature of TYPO3, but it has its disadvantages and weaknesses in other aspects.  It depends on the requirements of the project.
Answers.UserDisplayName: Marc 
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-04-29T12:20:35.267Z
Answers.LastActivityDate: 2024-04-29T21:11:09.027Z
Answers.LastEditDate: 2024-04-29T21:11:09.027Z
Answers.UserDisplayName: Mats Mikkel Rummelhoff
Body: <p>In TYPO3 (<a href="https://typo3.org/" rel="nofollow noreferrer">https://typo3.org/</a>), there are two approaches for multilingual websites known as the &quot;One-Tree&quot; and &quot;Multiple-Trees&quot; approach.</p>
  <p>The Multiple-Trees approach is no problem in Craft CMS: I know sites, sections and field translations.<br />
  But I have no idea for the One-Tree approach? (Don't know if it's even possible ...)</p>
  <h3>Multiple-Tree</h3>
  <p>The Multiple-Tree approach means that the different languages have no connection to each other and switching to another language loads the respective homepage.<br />
  Pros: Very flexible, because of separate pagetrees for each language.<br />
  Cons: No control of the translation status, especially for larger websites.</p>
  <h3>One-Tree</h3>
  <p>The One-Tree approach means that when switching the website to a different language branch, the corresponding content for the other language is loaded automatically. If there is  no translation available, the corresponding content of the default language is displayed. One page hosts all languages.<br />
  Pros: Good overview of the translation status of all pages in the backend.<br />
  Cons: All languages share the same pagetree (kind of inflexible).</p>
  <h3>Example from TYPO3</h3>
  <p><a href="https://i.sstatic.net/itUfToej.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/itUfToej.png" alt="Example from TYPO3" /></a></p>
  
Tags: <localization>
Title: Multi language: Multiple tree and single tree?
ThreadText: # Multi language: Multiple tree and single tree?
  
  (Asked by: username_0 on 2024-04-29)
  
  In TYPO3 (<https://typo3.org/>), there are two approaches for multilingual websites known as the "One-Tree" and "Multiple-Trees" approach.
  
  The Multiple-Trees approach is no problem in Craft CMS: I know sites, sections and field translations.  
  But I have no idea for the One-Tree approach? (Don't know if it's even possible ...)
  
  ### Multiple-Tree
  
  The Multiple-Tree approach means that the different languages have no connection to each other and switching to another language loads the respective homepage.  
  Pros: Very flexible, because of separate pagetrees for each language.  
  Cons: No control of the translation status, especially for larger websites.
  
  ### One-Tree
  
  The One-Tree approach means that when switching the website to a different language branch, the corresponding content for the other language is loaded automatically. If there is no translation available, the corresponding content of the default language is displayed. One page hosts all languages.  
  Pros: Good overview of the translation status of all pages in the backend.  
  Cons: All languages share the same pagetree (kind of inflexible).
  
  ### Example from TYPO3
  
  [![Example from TYPO3](https://i.sstatic.net/itUfToej.png)](https://i.sstatic.net/itUfToej.png)
  
  **Tags:** localization
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-04-29. Score: 2 | Accepted answer
  
  **Edit**: After the screenshot above was added in an edit, I realise that this question might have more to with how multi-site entries are managed in the control panel, and less with how the content itself is modelled, or how it's exposed on the front end.
  
  The short answer is that, no – there is no side-by-side or equivalent view for multi-site content in Craft, that is equivalent to the One-Tree TYPO3 view pictured above.
  
  In Craft, propagated multi-site entries can be switched between via the site dropdown in the top left corner of element edit pages and indexes.
  
  **Original answer** *(doesn't really answer this particular question, but the info might still be useful to someone coming to Craft from TYPO3):*
  
  I'm not familiar with TYPO3, but based on your description I'd say the closest equivalent to the One-Tree/Multiple-Tree concepts in Craft lingo is the term "propagation method" – i.e. in multi-site Craft installs, content can be configured to *propagate* across different sites, in different ways (or not at all).
  
  Sections (and Matrix fields) can be configured to propagate (or not) using mutiple different propagation methods. For example, you might have a section where all entries are propagated to all sites, another section that only propagates its entries to sites in the same site group, and even a section that doesn't propagate at all (i.e. equivalent to "Multiple-Tree"), etc.
  
  It's even possible to configure a section to let content authors *optionally* propagate specific entries to different sites, i.e. letting the content author decide if a particular entry should be available in multiple sites or not.
  
  Essentially, this means that in Craft, you can combine the One-Tree and Multiple-Tree approaches to multi-lingual content, and use one or the other (or combinations of the two), when and where it makes sense to any particular piece of content.
  
  Regardless of your approach to multi-lingual content modelling, the strategy for switching languages in the front end is completely up to you. To that end, it's completely possible to build a language switcher component that conditionally redirects the user to the same entry in the chosen language, or to the selected site/language's base/homepage URL if the current entry doesn't exist in that site/language.
  
  Here's [an example](https://craftsnippets.com/articles/universal-language-switcher-for-craft-cms?s=s) for such a language/site switcher component.
  
  Additionally, plugins like [GeoMate](https://plugins.craftcms.com/geomate?craft5) can be helpful in building language switchers (check out the [`craft.geomate.getSiteLinks()`](https://github.com/vaersaagod/geomate/blob/master/README.md#craftgeomategetsitelinks) method).
  
  I'd also recommend reading the ["Sites & Localization"](https://craftcms.com/docs/5.x/system/sites.html) guide in the official Craft docs, for a good overview on how multi-lingual content is approached in Craft.
  
  > **Comments:**
  > **username_0**: Hi username_1, thank you for your long and detailed answer ... this is very helpful to me!    Now I have an idea how to work with this topic, what possible within the control panel an what not.    Every single CMS has its pros and cons. This view in my screenshot is a strong feature of TYPO3, but it has its disadvantages and weaknesses in other aspects.  It depends on the requirements of the project.  
  
  ---
  
  