During the weekly dev meeting today, we brainstormed feature ideas and issues to potentially focus on for the 1.18 milestone. The idea was to see what feature ideas or UX improvements that people are most excited about. To be included in the 1.18 milestone, a new feature or improvement will need someone to advocate for it.
Here are some of the ideas we discussed. We'd love for you to:
- Comment on which of these ideas that you would most like to see in version 1.18.
- Suggest additional ideas.
- Think about which of these issues you would like to advocate for.
Here is a list of what we talked about:
High usage contrib projects:
Advanced Drupal Caching (a.k.a. cache tags and cache max-age)
Merge all the "Update core/module/theme/layout" pages into a single page. - klonos
File Field UI / Node title display settings on manage display page
Both of these require pseudo-fields to have settings #3859
Remove "tabs" from log-in, register, and password reset pages.
Missing D7 features
Provide "Delimited" and "HTML list" display formatters for fields
Which ideas/features/improvements get into 1.18 will depend upon a combination of which ones generate the most interest AND find a person willing to advocate for them during the release cycle AND find people willing to write the code and test the pull requests. Your input is needed now!
From the list above, I vote for 'Multiple screenshots for contrib projects'.
I'd also like to suggest a new candidate: 'Add Reference module to core': https://github.com/backdrop/backdrop-issues/issues/1301 & https://github.com/backdrop-contrib/reference
I like the idea of having something like Backup and Migrate in core. It could be a scaled down version of the module.
I'd love to see the reference module in core. But, that seems like a much bigger project that I'm not sure I can contribute to.
I'm also a big fan of getting accordion blocks into core. In specific, because I think they would be really beneficial on the dashboard page. It would be great if people could reduce the footprint of some blocks without removing them completely.
EDIT (10/11/20): Adding this to my list of favorites:
Add a help text indicator & tooltip for placing next to things that may be confusing
I like all the suggestions, I think Field group functionality in core is extremely reasonable - I've always wondered why such useful functionality is not among the standard tools for working with fields.
There is something I do manually for all my sites by adding new links to the Administration menu for the most commonly used administrative tools. I enclose a screenshot from one such modified Administration menu.
But it would be useful to have the Favorites article in the Administration menu and the possibility to add any desired administrative page to the Favorites, applied by selecting a check-mark on the administrative page. This saves a lot of time in the daily work of site administration.
In addition, I make such custom items in the Administration menu to facilitate the work of users - without giving access to all items in the Administration menu - which only confuses them and they do not need, I give them only individual tasks that they can do on a comfortable place. Something like User menu, but not in a separate block but in the Administration bar itself.
In short, I suggest that the Administration bar has standard Favorites and User menu items and the ability to easily add and remove selected administrative pages there, through options on the administrative pages themselves.
This is a nice idea. Like D7 Shortcuts module but in the Admin Bar.
The Shortcut module was intentionally removed from Backdrop core with https://github.com/backdrop/backdrop-issues/issues/76 (early on, back in 2013), before 1.0.0 was released.
It currently lives in contrib: https://github.com/backdrop-contrib/shortcut (@alanmels ported it a couple of weeks ago 🙂 ❤️ )
Thank you Tim for opening the discussion... here are my favored points, sorted by priority
I'd like to see our several update pages get merged (#2714) (core/module/theme/layout). This UI is currently pretty confusing.
And I'd like to see the HTML details element in core form API (#324).
Unfortunately I can't advocate for either, because I'm already advocate for webp support in core.
@indigoxela I plan to advocate for (and also work on) the "Merge all update pages" issue for this cycle 😉
I'm advocating for an exposed filter in the image library.
Well, being late to the party! Here are my favorites: