As we briefly touched on at the Backdrop Summit, one of the biggest UX challenges in Drupal has been the most recent version of the Views UI, which rearranged all the options in a way that baffles even seasoned drupal developers. Mindbogglingly, this doesn't seem to have been addressed at all when they migrated the Views module into Drupal 8 core, so improving this problem could be a great opportunity to show how Backdrop could become the more-usable alternative to Drupal.
One idea that I've had is to use vertical tabs to organize the different aspects of views configurations. It would kinda be like the top-to-bottom configuration workflow from Views 1, but with less scrolling. I'm thinking the tabs for each view display could be something like: - Content selection (base tables and relationships) - Filtering (both regular and contextual) - Display type (configuration and fields, if applicable) - Header, footer, and empty text - Additional settings (permissions, caching, query settings)
Does this sort of approach make sense? Perhaps we could create a contrib module for this alternate UI now, and then consider merging it into core for backdrop 2.
Recent comments
Hi Rob, Welcome to Backdrop! Here’s a quick overview: Subtheming Bootswatch: You should create your subtheme based on Bootstrap5 Lite, not directly on a Bootswatch style....
Basic Theme designing questions, using Bootstrap5 Lite
Hi Rolf, This happens because CKEditor saves absolute or semi-absolute paths in the HTML instead of using Backdrop’s file stream wrappers (like public://). When you move your site...
Losing link to embedded pictures when moving my installation
The error means the Stripe client isn’t initialized — $stripe is null. Fix steps: In CiviCRM → Payment Processors, ensure valid test/live API keys are entered and match the mode...
Getting Error after submitting event register form By using Stripe Payment Processor