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.

CommentFileSizeAuthor
#1 1350674.patch7.85 KBRobLoach
screenshot30.png38.03 KBRobLoach
screenshot29.png57.46 KBRobLoach
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

RobLoach’s picture

Status: Active » Needs work
FileSize
7.85 KB

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

markdorison’s picture

Version: 8.1.x-dev » 8.3.x-dev
Status: Needs work » Closed (outdated)

The D8 block configuration UI now has a 'CATEGORY' column which I believe addresses the ultimate goal of this ticket.