The answers are not from enough people to have a significant weight. We may do a voting about this.
My feeling is that once “TypoScript syntax” and “TypoScript Templates” are more clearly used to differentiate (and the term just TypoScript is avoided), it would already be a big improvement. With the renaming of the “TypoScript Reference” to “TypoScript Template Reference” I see this task as mostly done and the rest is cherry on top. In other parts of the docs, the terms are already used as suggested.
I do not see so much a problem with TSconfig, but this does not mean I want to entirely dismiss the suggestions. Just not sure about that right now.
To summarize the proposals (see above):
TypoScript
TypoScript: Syntax of configuration
Template: Configuration for Frontend using TypoScript
In addition to the proposal of Sybille, I would rename … [suggestion for TSconfig follows]
I would interpret this to mean: agrees with me on terms of TypoScript
I’d use TypoScript for the syntax or ‘language’.
The contexts are “TypoScript templates” and
For me, your answer is a little ambigous what you are suggesting
TypoScript = syntax for everything
I guess, you mean the term TypoScript would refer to the syntax. But then you say
TypoScript itself is for me just everything what is in the template editor in the setup area
TSconfig
PageTs
UserTs
User TSconfig” and “Page TSconfig”
rename Page TSconfig to PageConfig
rename User TSconfig to UserConfig
Moreover I opt for …
TSconfig
(as is now)