Problem/Motivation
When looking at the Blocks administration page, the user is presented with a huge list of random Blocks with absolutely no context associated with each one.
A good example is the "Syndicate" block. Noone knows where that's coming from, or what that's trying to syndicate. If we were to namespace it with "Node", or "System", then the user has a better understanding of what the block does.
Proposed resolution
If we were to namespace each block with the module name, it gives the user a better understand of where the Block information is coming from. Provides some context to each block, helping them make sense to all the random information on the page.
Remaining tasks
- Clean up the patch more. Decide on whether this is a worthy step.
User interface changes
The Blocks administration is cleaner, and now has some context to it.
API changes
No API changes, module developers are now encouraged to namespace their blocks with their module name.
Comment | File | Size | Author |
---|---|---|---|
#1 | 1350674.patch | 7.85 KB | RobLoach |
screenshot30.png | 38.03 KB | RobLoach | |
screenshot29.png | 57.46 KB | RobLoach |
Comments
Comment #1
RobLoachComment #3
markdorisonThe D8 block configuration UI now has a 'CATEGORY' column which I believe addresses the ultimate goal of this ticket.