Problem/Motivation
Current library block and components provide multiple display options.
It looks nice to address power users but the flexibility of display create permutations nobody test.
Partially related to #3569409: Improve UX by restructuring "Libraries" and "Blocks" island
Proposed resolution
Keep for now only what provide a real difference for the user.
Will have future issues if needs evolution based on real users feedback. Then we'll be able to include better coverage of permutations.
Components:
- grouped -> default
- with variants
- flat list -> remove, provide no value
- thumbnail mosaic -> remove, provide no value and require the theme to provide thumbnail
+ add description to explain the difference for 'with variants'.
Blocks:
- grouped -> default
- flat list -> remove, provide no value
So as it's one option, remove the option.
Then adapt existing 'flatten' but without presets and that respect displays:
- Components default + Blocks default
- Components variants + Blocks default
Comments
Comment #2
pdureau commentedThere is another approach, I don't know if it is a better one but this ticket is a good opportunity to discuss.
Are we sure we keep
variants? We are not sure it brings value:If we remove it, it will allow us to solve what may be the reason of the confusion here. The existing list (grouped, flat, mosaic) is merging 2 orthogonal concepts (grouping and displaying) and could be split in 2 distinct settings.
What do you think?
Great. It would be better without the presets.
Comment #3
mogtofu33 commentedIf we do not keep
variantlet start clean without option for user and grouped by default.It was the only feature with impact to the user as it provide a really different list and avoid selection of variant after drop, but if we consider it is a rare occurrence then we can remove.
This will re-create the permutations with low benefits for the user, it expose the same things with few differences, so would be something to evaluate later with user feedback.
As user I never change this option because the feature was the same, so no need to provide user with it.
Comment #4
mogtofu33 commented