#107521Yaml-based Backend Layouts / Page Layouts
Description
I think we should standardize our configuration more and more into
a) naming: “Page Layout” instead of “Backend Layout“
b) configuration language: Use common standards over custom pageTSconfig
I think we could use a yaml-based backend layout data provider.
Reviews 1
Files 1
History 78
-
Gerrit Code Review pushed patch set 1 for main to change 90766 status
NewUnder Review <span data-processor="relativetime" data-value="2025-09-22T19:38:48+00:00" > 09/22/25, 19:38 </span> -
Jigal van Hemert commented <span data-processor="relativetime" data-value="2025-09-24T10:33:26+00:00" > 09/24/25, 10:33 </span>
-
Benni Mack commented <span data-processor="relativetime" data-value="2025-09-24T19:08:06+00:00" > 09/24/25, 19:08 </span>
Jigal van Hemert wrote in #note-2:
> Sorry, but this can be part of a third party solution.
Yes.> There was a very good argument for a TSConfig based backend layout provider which could change the available BE layouts for a part of the page tree of an installation.
This should be still the case ofc, I consider this a requirement.
> The argument of “common standards” is very minor to me. Yaml leans heavily on indentation which complicates the overview of large files. Simplifying the structure with imports requires third party solutions – a symfony package.
YAML is more known than PageTSconfig in the non-TYPO3-World. I’d like to find solutions that make it easier to configure page layouts, and I re-opened my latest v13 project where I have 80 lines of pageTS to define a backend layout. I will attach it, and I think it is horrible – just plain horrible – for new people to get to know TYPO3.
> The remarkable thing is that symfony is moving away (for some years already) from yaml in favor of PHP for internal configuration.
I would say that more people use .gitlab-ci.YAML files than configuring symfony via PHP. But I think we’d need a market research to find hard numbers.
That being said, we could also introduce a PHP or JS-based provider. would love that as well. I’m fine having multiple ones.> The argument that yaml is easier for inexperienced users/integrators is only marginal. Most people understand TS syntax after a minute of explanation. Both yaml and TypoScript/TSConfig will be converted to PHP so that could be an argument to use PHP instead of Page TSConfig and surely instead of yaml.
That being said, TypoScript parsing + caching is much more expensive than parsing Yaml.
Yaml has had bad reputation for TYPO3 due to EXT:form, and I am 100% with these people here, but I like especially because we can parse it statically (like JSON). PageTSconfig could allow TypoScript conditions, and that makes it very very unstable. That was one of the reasons for site configuration not being written in TypoScript.
-
Benni Mack changed attached jigal.tsconfig <span data-processor="relativetime" data-value="2025-09-24T19:08:26+00:00" > 09/24/25, 19:08 </span>
-
Soren Malling commented <span data-processor="relativetime" data-value="2025-12-04T08:25:40+00:00" > 12/04/25, 08:25 </span>
Can we include the fact that a backend_layout might be layout-specific. So loadable from a siteset instead of extension and global config folders
-
Benni Mack commented <span data-processor="relativetime" data-value="2025-12-04T09:18:11+00:00" > 12/04/25, 09:18 </span>
Soren Malling wrote in #note-5:
> Can we include the fact that a backend_layout might be layout-specific. So loadable from a siteset instead of extension and global config foldersI’d love that :) Probably unrelated though?
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:01+00:00" > 04/21/26, 11:23 </span>
-
Benni Mack changed status
Under ReviewRejected <span data-processor="relativetime" data-value="2026-11-09T11:08:07+00:00" > 11/09/26, 11:08 </span>
Sorry, but this can be part of a third party solution. There was a very good argument for a TSConfig based backend layout provider which could change the available BE layouts for a part of the page tree of an installation.
The argument of “common standards” is very minor to me. Yaml leans heavily on indentation which complicates the overview of large files. Simplifying the structure with imports requires third party solutions – a symfony package.
The remarkable thing is that symfony is moving away (for some years already) from yaml in favor of PHP for internal configuration.
The argument that yaml is easier for inexperienced users/integrators is only marginal. Most people understand TS syntax after a minute of explanation. Both yaml and TypoScript/TSConfig will be converted to PHP so that could be an argument to use PHP instead of Page TSConfig and surely instead of yaml.