TYPO3 Core

Feedback from Surfcamp 2024¶

The feedback was good in general, people understood the concept and the naming did not really raise question. The last-minute switch from profiles to sets was right, the name "profile" would have been too mistakable according to some participants.

The dependency mechanism was used, but people needed some help to get to the idea that set's can be composed of multiple subsets in order to structure own code with multiple sets

Some random notes from different chats with the participants that tried this feature in their surfcamp projects:

• Documentation should focus on set configuration first, as direct TypoScript configuration in config/site should be a rare case.

• TypoScript records overview shows no site/set-titles if no websiteTitle is defined in site config: maybe show labels of enabled sets as an additional explanation (or just site-set)

• Desire: Let EXT:frontend provide to a default set for PAGEVIEW

• Explain that constants.typoscript is not actually needed and settings.definitions.yaml should be used instead constants. constants.typoscript in sets and site config is basically only available if really needed

• settings example mixes settings and definition.

• Per language settings

• Straight forward way/suggestion for registration of Form configuration?

• We may need secondary-sets, like full sets, but not selectable in the UI directly.

• We need a UI for the sets: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83879

• How to use "multiline text"

• When choosing colors, it would be cool, if one could choose a "color palette" which automatically sets up multiple colors.

• Conditions: Choosing "enable cookie consent" should then show available options when choosing "cookie consent mode" such as Cookie BOt (this needs an ID) or User Centrics (needs some other identifier),

• Selecting a file (e.g. logo) is required: Sometimes from FAL, or from an extension path or just "upload" a file

• Limit the list of available forms within a set

• Information in backend for invalid site dependencies (not only in var/log)

• Relative import in site page.tsconfig

• Settings in YAML should support environment variables, e.g. %env(SOME_API_KEY)%

• by andy, post surfcamp: Documentation should explain why core sets are named typo3/foo instead of typo3/cms-foo, while regular packages should use vendor/package name as-is