ErHaWeb, 23 days ago

@brotkrueml Thank you very much for the great instructions. This is useful for my v12/13 extensions.

To be able to structure TypoScript files better, I like to import entire directories that can contain several *.typoscript files. So far I have used the directories Constants/ and Setup/ under Configuration/TypoScript/.

Would you leave these directories there in future or also move them to Configuration/Sets/<Identifier>/?

ErHaWeb, 23 days ago

@brotkrueml
The fact that these are TypoScript files, which have historically always been located under Configuration/TypoScript/, speaks against the move.

An argument in favor of the move is that the included files belong to the site set.

Finally, the question remains whether there are any technical problems if additional directories are created in the site set folder.

brotkrueml, 23 days ago

@ErHaWeb Good question. I think, if TypoScript is only used by a specific site set I would move it there (to have everything at one place). Also consider the note in the changelog: "import statements are still fine to be used for local includes, but should be avoided for cross-set/extensions dependencies."
https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.1/Feature-103439-TypoScriptProviderForSitesAndSets.html

So, technically there's nothing wrong with either option, it's more a question of consistency IMHO.

ErHaWeb, 23 days ago

@brotkrueml Thanks! Ok, I was only referring to local includes, so @import is still good for structuring complex TypoScripts.

Thinking about it, it also seems more logical to me to move the directories to Configuration/Sets/<Identifier>/ where they belong.

Everything under Configuration/TypoScript is then reserved for the global, cross-site TypoScript code, if necessary at all.

From v13 onwards, it will probably often be possible to dispense with Configuration/TypoScript/ altogether.

brotkrueml, 23 days ago

@ErHaWeb Yeah, put under Configuration/Typoscript/ everything that is required installation-wide, mostly in a site package installation. And the other stuff into a site set. And third-party extensions should provide everything in one or more site sets. This way it is easy to add, for instance, for one site the news configuration and for another one not. This unclutters the configuration in multi-site installations a lot.