Epic #103630
Updated by Benjamin Franzke about 1 month ago
h3. Feedback from Surfcamp 2024 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:frontent 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.