Posted by lisarex on November 9, 2012 at 12:48pm
6 followers
| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | views_ui.module |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
| Issue tags: | BADCamp2012UX, Usability, VDC |
Issue Summary
In Views usability testing we uncovered a disconnect in the workflow of adding a block, as you have to create the block display, then save, then go out to the Blocks UI.
In addition to #1836390: Add “place block in region’ to the Views wizard to help workflow, “place block in region” to the views UI would also be helpful.
We need to figure out the wording but I think something like 'Placement: None' as the default could work.
Comments
#1
Possible location for change attached
#2
Actual wireframe; needs review.
This solves a couple problems:
a. They know where the block shows up (if at all)
b. They can place the block in region without taking them away from the Views UI / interrupting their flow
Note that any block-related configuration beyond adding/removing the block to a region requires a trip to admin/structure/block
#3
Thanks for the mockup.
One question is whether it makes sense to have this kind of workflow if #1535868: Change notice: Convert all blocks into plugins got in.
That patch forces you somehow to create an actual block instance in the block library,
so the workflow seems really special/different compared to your approach.
#4
That patch is very close, and indeed changes the interaction patterns with blocks, so postponing on that.
#1535868: Change notice: Convert all blocks into plugins
#5
As a side note, views could also extend the add custom block workflow in order to allow users, create a new views block.
Just a idea and currently not really the Drupal workflow, but being able to start creating a view/display from within the block configuration page might make sense in the context of this issue