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?

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).

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.

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

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?

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).

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.

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?

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).

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.