The UX team decided it would make more sense to have the block placement sidebar to the left of the block layout listing.
When the window is at small sizes, the block placements sidebar will continue to fall below the block layout.

Comments

Status:Active» Needs review
StatusFileSize
new11.53 KB
PASSED: [[SimpleTest]]: [MySQL] 58,435 pass(es).
[ View ]
new14.63 KB

The first mistake I made in the original issue (#2058321: Move the 'place block' UI into the block listing) was to use "left" and "right". This issue highlights the stupidity of that decision :)
So the first thing I've done here is rename them "primary" and "secondary".

Locally I did this in several patches, and I've attached one rolled with format-patch to make it easy to see the discrete steps.

StatusFileSize
new149.49 KB

Screenshot of it on the left.
Screen Shot 2013-08-31 at 2.07.50 PM.png

Two things that pre-existed but are now more obvious:
The weird gap caused by "Show row weights"
There are three greys used: The two by the block placement details element (coming primarily from the node form, see https://drupal.org/node/2061863) and the one for the block layout listing header.

I don't think this was a UX team decision at all, as far as I know mostly Kevin liked it this way. I am definitely not for doing this and I don't know if yoroy is. The case that was made is that the sidebar is for "secondary" content and can thus be overlooked. I think there are at least 3 points, on which this UI change could cause issues:

1) As we add more and more usefull stuff like facets in the sidebar. The strategy of "people might ignore it", becomes rather silly. Because people ignore it, because we don't put critical functionality there, once we do - people learn that its there. Its not like the Views UI, where you have a cockpit of elements - the sidebar is highly noticeable.

2) Grouping occurs when its put on the left. The vertical menu, conflicts with the sidebar making it look like a group of links (even though there is a visual divider, the spacing, items, etc. all look similar). Given that vertical listings that look similar are so close to each other, it will likely make it harder to scan down the list.

3) This also sets a precedent that people can just decide where they want their sidebar, on the left or right. If we do this it really needs a bunch of rules, because we don't want the UX to become so random, once contrib starts using this pattern.

Priority:Normal» Major
Issue tags:+blocker
StatusFileSize
new12.86 KB
PASSED: [[SimpleTest]]: [MySQL] 58,426 pass(es).
[ View ]
new10.11 KB

After working on #2079037: Use two columns for the place block form and studying the approach used in node form more, I realized that polluting the form with all of this knowledge of primary/secondary left/right is wrong.
With a template file, I can just target what we want to move, and leave the form structure as it was before #2058321: Move the 'place block' UI into the block listing went in.

As this changes all of the structure of the block listing (back to how it was), it blocks #2078951: Highlight the row of block that was just placed and #2079037: Use two columns for the place block form.

No visual changes are made here.

Priority:Major» Normal
Status:Needs review» Needs work
Issue tags:-blocker
StatusFileSize
new1.72 KB
PASSED: [[SimpleTest]]: [MySQL] 58,700 pass(es).
[ View ]

Because this doesn't have consensus, I've moved the form restructuring to #2079761: Use a template for the block listing page to simplify the form, and am demoting this back to a normal task.

Here are the changes, assuming that issue goes in as is.

Leaving at NW because it will fail otherwise.

Status:Needs work» Needs review

Okay, that went in.

StatusFileSize
new1.72 KB
PASSED: [[SimpleTest]]: [MySQL] 58,984 pass(es).
[ View ]

Rerolled for recent commits. No changes. The screenshot in #2 is still accurate.

Assigned:tim.plunkett» Unassigned
Issue tags:+Needs usability review, +Needs design review

Unassigning from myself, the patch still applies.

Nothing to review I think, it was reviewed in #3. And those comments need to be addressed.

Status:Needs review» Needs work

Patch no longer applies and it seems we need to have more of a discussion about this issue anyway so setting back to NW.

Personally I preferred it on the left however it's been growing on me over on the right, so i'm happy for someone else to decide where it ends up.

Status:Needs work» Needs review
StatusFileSize
new1.93 KB
PASSED: [[SimpleTest]]: [MySQL] 63,181 pass(es).
[ View ]

Maybe something like this?