Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comment | File | Size | Author |
---|---|---|---|
#2 | block-region-1.jpg | 94.85 KB | lisarex |
#1 | place block.jpg | 86.83 KB | lisarex |
Comments
Comment #1
lisarex CreditAttribution: lisarex commentedPossible location for change attached
Comment #2
lisarex CreditAttribution: lisarex commentedActual 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
Comment #3
dawehnerThanks for the mockup.
One question is whether it makes sense to have this kind of workflow if #1535868: 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.
Comment #4
tim.plunkettThat patch is very close, and indeed changes the interaction patterns with blocks, so postponing on that.
#1535868: Convert all blocks into plugins
Comment #5
dasjoAs 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
Comment #6
mgiffordComment #7
yoroy CreditAttribution: yoroy at Roy Scholten commentedInteresting bit of workflow to create wireframes/prototype for.
Comment #8
yoroy CreditAttribution: yoroy at Roy Scholten commentedComment #9
tim.plunkett#4 is an understatement.
Now that blocks can be placed an infinite number of times, we need to decide how to represent that ability.
Here are some additional questions:
Comment #10
Bojhan CreditAttribution: Bojhan as a volunteer commentedGood questions, much of this idea was before the block concept was fully worked out. We might have some "flooded" pattern issues, as we place dozens of block instances but that might just be rare.
1) I am not sure, what is best there?
2) Yes, I think this ought to be a two-way street and makes people more aware that the two are connected.
3) I think this goes both ways, you would be able to remove as well. We should treat it as one "truth" so all actions should go both ways.
Comment #25
Lendude#2087219: Allow views blocks to be placed from the Views UI closed as a duplicate, not sure this is still something we want to do. We provide something for pages, so maybe we should for blocks? Not sure how many blocks still get placed via the block interface?