The layout of the list and tree view is a compromise between a compact list of elements and a generous enough layout to work well on tablet devices. It works well for e.g. a small set of pages, but we also know (and also get feedback that supports this) that it fails in a variety of other cases:
- Tree levels are not always clearly discernible, as the large padding between rows and the horizontal lines dissociates content that would be easier to read if it was shown in a more compact layout.
- We have some trees and lists with a lot of nodes, sometimes even on a single level. For these trees, it would be beneficial to see significantly more rows at a time to avoid heavy scrolling.
- The rows and arrows on tablet devices are actually still too small on tablets to work comfortably and safely - we had a larger padding before, which worked best on these devices.
There's actually no one layout that works well on all devices and in all views. We thus want to offer the user the choice between a small set of layout options with different density levels: a generous, a normal (the current) and a compact appearance of a list and a tree.
- For regular, "non-technical" content such as Pages and Assets, Events, etc., we show lists and trees using the current, normal layout on desktops and using the generous layout on tablets.
- For "technical" content or sets with lots of items, we would use the compact layout on desktops and the normal layout on tablets.
- For every tree and list, the user has the option to choose a different layout than the default layout still.
This issue mainly covers the different layout options and how we choose them. Next steps will be to persist a choice across app restarts and to allow to choose a layout for a given layout in a user's profile.