I really hate the separate page to show the regions for each theme. That link to the regions page doesn't even show on the Block Admin page at all times. I saw that link once, but not again; and I do not see how to get back to that regions depiction page. Having those regions identified on the Block Admin page was sooooo much better. I cannot think of any good reason that was broken out. And, I am dreading the time wasted on this UI change.

It is one thing if you have only 1 website theme that you work on regularly. It is another to be working on 20 different projects/themes at once time, and not all of them regularly. It is important to have a quick/easy reminder of those regions.

CommentFileSizeAuthor
#2 scr_block-admin.jpg74.24 KBgreta_drupal

Comments

Jeff Burnz’s picture

The link is on the block admin page - admin/structure/block

The UI change is a core change, Bartik can't do much about that. I actually like the change since now i have more room for the table to expand and its not all crammed up + often times I think the block regions were a distraction, although in the beginning I can see how they can be helpful. Now I just open the block regions example page in another tab.

greta_drupal’s picture

StatusFileSize
new74.24 KB

I beg to differ. See attached. No link to the demo page.

Jeff Burnz’s picture

Status: Active » Closed (works as designed)

You have help module disabled or you moved the block somewhere where it does not display in overlay.

greta_drupal’s picture

Status: Closed (works as designed) » Active

Ah, there is now a movable system message block. Didn't realize that. But, I like it! ...Got excited for a minute that I could choose its location. But, alas, I tried it in a sidebar for only admin/* pages and it didn't show. I'll have to play with it more.

Jeff Burnz’s picture

Highlights a weakness though doesn't it (actually a real wtf imo), if you move help to a region that doesn't display in Overlay you loose critical functionality - you can't even view the regions. Sidebars never display in Overlay, if you switch overlay off they will show as per normal.

greta_drupal’s picture

Yep, that is exactly what I did. And, I can see non-tech clients/staff doing that easily.
So, I'd agree that was probably not a good UI decision.

I was trying to quickly do a D7 site for demo, and when I lost the regions it was frustrating. I had no idea how to get back to that info. I thought that wasting 15+ mintues hunting for it, then another 15 minutes to post about it, and X minutes to get a response was an unreasonable effort.

And, it isn't like the sidebars are name logically: "sidebar right" and "sidebar left". ("Sidebar first" and "Sidebar second" imply stacked, to me.) And, "Triptych first", "Triptych second", "Triptych third"? Seriously? I've been a writer for 20 years, and I had to look those up -- not words that roll off the tongue in everyday use. This whole region naming had me scratching my head. The idea of Drupal 7 is to be less intimidating to novice users. If you are going to bother to change "Users" to "People" (was that really necessary?), why go with such obscure words for regions? I think that it will be offputting to end users. I'd call it a faux pas, but I'd never use "faux pas" in a user interface. *grin* ...I'd be curious to see the useability studies that lead to this decision.

If the regions had been named "Sidebar left", "Sidebar right", "Middle left", "Middle center", "Middle right"...the regions guide would be less important. (Middle implies vertical position -- "midriff", "middle child", "middle Earth", etc. "Left", "Right", "Center" = horizontal position. That makes sense. "First...Middle...Last" not parallel construction.)

To me Help is user input instructions. Something as essential as a layout guide I would not call "help". So, I would not have made that UI decision, personally.

jensimmons’s picture

Version: 7.0-beta2 » 8.x-dev
Component: Bartik theme » block.module

Greta, you've started to talk about two different things in this one issue.
1) Your desire for the listing of regions for block placement to be in a different place;
2) Your desire for the Bartik regions to be renamed.

If you want to talk about a second thing, you need to open a separate issue. But before you do, you should go read about why regions are named "sidebar first" instead of "left sidebar". This is so that international languages can be supported, and the sidebars can be switched from one side to another as a site is changed into another language. There are long debates about this change on other issues on drupal.org.

As for the region map being separated from the block interface — I am guessing that was done in order to support the overlay. I'm sure there are discussions about that decision elsewhere as well, if you want to read about why it was done. Honestly, we all agree that everything about the block interface is a giant WTF at this point. That's why there is a whole movement to change it radically — called "Butler". You can help out, and help make Drupal better.... checkout http://groups.drupal.org/butler

Since the original post is about the block interface, I am changing the component to block module. Also, this request is too much of a change to happen for D7, so I am moving this to D8.

greta_drupal’s picture

Greta, you've started to talk about two different things in this one issue.
1) Your desire for the listing of regions for block placement to be in a different place;
2) Your desire for the Bartik regions to be renamed.

My points are interrelated. The point (as stated) being that since the regions names are not particularly intuitive, the regions guide is all the more important.

I have merely offered my user experience feedback, not made any demands (desires) upon the design team.

jhedstrom’s picture

Version: 8.0.x-dev » 8.1.x-dev
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs issue summary update

Tagging for IS update (I think there may be some duplicates out there about re-working the block admin UI).

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

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now 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.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

More information about this issue was asked for in #9, 6 years ago. No additional information has been supplied, therefor closing.

There is a meta that may be of interest,#2673758: [meta] Usability issues with the Drupal 8 block system

Thanks