TYPO3 Core

1. We need to resolve the introduced @todos in the initial commit

2. Add tests for the new APIs

3. Create test cases for 1000 sites and find the performance bottlenecks

4. Create an API to fetch all language objects for a page and use that in the BE to encapsulate all calls to sys_language. Also encapsulate this for the TSconfig option for defining the "default language" options in TSconfig.

5. After 4 - go through page module, list module, view module and use site handling in there

6. Make rootline resolving better / faster (question is: how)

7. Allow to make a site configuration "read-only" and respect that on a per-

8. Add TypoScript conditions [site = site-identifier], and [siteLanguage = de-DE] (no languageId please!)

Discussion points.
- How should we consider pages with "non-sites"? Convert non-sites to pseudo-site? having sys_domain as fallback?
- How to handle schema- and domain-less bases? "/site1" and "/site2" are valid sites - especially when it comes to nesting
- How to handle http+https in a site base?
- How to handle multiple domains in one site? placeholders?
- How to handle "is_siteroot"? Upgrade wizard to give all root-level pages "is_siteroot"?
- How to deal with storage folders that are not within a site?
- How to handle record translations in page/list module which are there but not available for the current site setup?
- How to handle a new language which should not show up yet on the live setup (yet)?
- How to handle language fallbacks properly for content records (what should we allow, and how to implement this?)