TYPO3 Core

Configuration/TsConfig/Page/
and
Configuration/TsConfig/User/

is the way to go IMO.

See also merged patch: Unify spelling for TSconfig

That doesn't make the decision easier, does it?

But a completely different approach would be to rename TSconfig to what it actually is: BackendConfig

So what do you think Sybille? What's your proposal for Txxonfig?

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

See also decision: https://decisions.typo3.org/t/clarification-of-term-typoscript/560/7?u=sypets

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!

Fun fact about naming of TSconfig:

Typescript uses the term "TSConfig", e.g. "TSConfig Reference" and tsconfig.json

https://www.typescriptlang.org/tsconfig

It's about time to rename TSconfig completely => BackendConfig