Directory names for TSconfig not consistent and also not consistent in docs (CGL, T3 Explained)
backend/Configuration/TSconfig felogin/Configuration/TsConfig form/Configuration/PageTS frontend/Configuration/TSconfig linkvalidator/Configuration/TsConfig
It's sometimes TSconfig or TsConfig.
And it's sometimes Page in TsConfig or PageTS.
Issue was raised in docs where it is also inconsistent:
I don't know which way should be the "correct" way.
I found the discussion in decisions which is usually used to decide these things:
But the final post with the results does not mention the folder structure:
Updated by Sybille Peters 8 months ago
I haven't looked at this for a while so can't say off the top of my head.
But a completely different approach would be to rename TSconfig to what it actually is: BackendConfig
There was a suggestion to rename TSconfig to PageConfig and UserConfig.
Now you are suggestion BackendConfig. I think it is good to have the word Backend in there. But there is also other backend config, such as extensions configuration, $GLOBALS['TYPO3_CONF_VARS']['BE'], etc..
How about, "Backend Page Config" and "Backend User Config"
but these terms are too generic. I think it is good to have something like Flexforms which is very specific.
or "Page BackendTSconfig" and "User BackendTSconfig" - too long.
Also, I would differentiate between used in file / directory names and used in text (docs, BE GUI), so it might be
- "Page BackendTSconfig"
- and Configuration/BackendTSconfig/Page
I think this needs some tweaking.
There are 2 things to consider
1. What would be the best terms
2. Should we really change it because there will be lots of changes, confusion and collateral damage. (e.g. change translations, how do you even translate these things, add redirects in docs, rename files in core, change in docs) - God help us!