[meta] Reorganize Block items in the administration menu

I think this makes a lot of sense. The block management all being stuffed away under the structure menu just feels a little awkward as in many cases blocks are more content than structure as far as users are concerned.

Thanks a lot, please also see #3273172: [META] Improve UX for block layout administration page which I created some months ago. Seems to be quite similar?

Fwiw, we have custom code doing similar rejigging on our client projects. This has considerably improved the UX for our clients creating blocks, including moving menu items, removing the redirect to add the block plugin when adding a block content entity, and various permissions changes.

We have also chatted through these issues a bit between some devs at PreviousNext and all agree they are good improvements.

Brought this up amongst our Drupal developers and everyone agreed it made all the sense in the world. Also with moving the block library it will allow users easier access and make blocks more usable.

I presented this to our central website development team at UoE.

The team has a good mix of developers, designers and site builders. The Drupal experience in the team also ranges from beginners to experienced.

Big thanks to Benji for putting together the slide deck, it made presenting this so much easier!

There was general support for this change and no objections, with one person voicing strong support for this.

There was one interesting general observation about the admin UI structure, the person felt that sometimes they spend a lot of time jumping around to different screens just to accomplish one task. That wasn’t specific to this issue and is more relevant for #2755613: Restructure the admin interface Information Architecture. I have some ideas on how we might improve to that experience, but again, that is out of scope for this issue.

So overall the ideas in this and the child issues were well received.

So full steam ahead!

I’ve noticed that I’ve only posted the general feedback about the proposed changes at the Austin Drupal Dojo in the thread on Slack (https://drupal.slack.com/archives/C1AFW2ZPD/p1666965008595329) but not in here yet. Apologies.
Here is the collective general feedback for all the three meetups I've presented and discussed the plans with so far. For reference I'll add the d.o user names, in case attendees have one, as well as some demographics in regards of the experience level and their general roles. The comments they've provided during the discussions I will split up and sort them into the relevant child issues accordingly.

Drupal Dojo Austin
Attendees: @arcticcheetah, @rocketeerbkw
Roles: front-end developer & site builder, backend developer
Experience Level: intermediate to experienced (1 to 13 years on d.o)
General feedback: thumbs up

Drupal Munich Weekly Lean Coffee Table
Attendees: @drubb, @franz-m, @it-cru, @jurgenhaas, @martin-mayer
Roles: site builder, backend developer
Experience level: experienced (13 to 17,5 years on d.o)
General feedback: Thumbs up

Fox Valley Computer Professionals:
Attendees: Anthony E. Scandora, @bsnodgrass, Sally Gradle, @TBone242
Roles: site builder, front-end developer (mainly in WordPress with experience in Drupal), Salesforce admin & developer (previously active in Drupal).
Experience range: intermediate to experienced (4 to 16 years on d.o)
General feedback: Thumbs up

I presented this issue and the recommended solution at the Sydney Drupal Users Group on 18 Nov 2022.

There was a resounding agreement from all attendees:

• Murray Woodman
• Julia Topliss
• Margery Tongway
• Max Pogonowski
• Michael Richardson
• Jim Koutsouris
• Marji Cermak

I presented this briefly at the Drupal Scotland committee meeting. The meeting attendees are experience Drupal site builders and developers, having worked on many client projects. They all reacted positively to the proposed changes. A couple of people noted that once they saw the proposed changes, moving Block Layout to appearance and Custom Block Library to content (and renaming Custom Blocks to Content Blocks) made a lot of sense.

The clients I work with also understand Blocks to be a form of content, so I agree that moving the Block Library to content makes sense. As a sitebuilder, I also agree with the other proposed changes (eg: #2987964: Move custom block types admin link to admin/structure

As someone who has presented many sessions/workshops on Drupal site building, I think this is a welcomed change. I always emphasize the importance of understanding how pages are composed so that people know where to go when changes to the site are needed. The proposed restructure provides a clear distinction between what is content and what is configuration relate to blocks. It also consistent with how other entities manage their respective content and configuration elements.

To some of us who have worked with Drupal for many years, it might be confusing at first. But I don’t think we should stop making progress just to keep things as they have existed in the past. The new locations make more sense. And for new people, it would be more intuitive.

I 100% agree with the proposed changes. Most people don't know that Block Types exist and this would give it more visibility.

#2987964: Move custom block types admin link to admin/structure is done, moving onto #2862564: Move Custom block library to Content.

Adding #2317981: Move block content edit and delete routes under admin/content/block to improve IA for editors and fix breadcrumbs as in scope for this work.

Adding #3333673: [PP-1] Add a local action on the block library as a "sub-task" of #2862564: Move Custom block library to Content.

Would like to add #1975064: Add more granular block content permissions as a priority after step 2. We have already moved block library and block types out of the block layout. But they are still under the administer blocks permission so this becomes a priority I think.

I agree that this makes #1975064: Add more granular block content permissions higher priority, as with splitting this up it becomes more obvious that more than one permissions is needed.

Although, I think we should put it after #3318112: [PP1] Move "Block layout" from Structure to Appearance, because once that is done the major reorganisation work will have completed, and then we will have a more holistic view of what permissions are needed.

#3333383: Create a redirect for the new Block types path is done 🎉 which now unblocks #1975064: Add more granular block content permissions. Retroactively adding it to the list.

#2862564: Move Custom block library to Content was committed!

This now unblocks #3318112: [PP1] Move "Block layout" from Structure to Appearance and #2317981: Move block content edit and delete routes under admin/content/block to improve IA for editors and fix breadcrumbs.

Just filed #3344314: [PP-1] Review the local task and page order/titles/labels under Appearance, not directly part of this work, but it is related as it's now a follow-up to #3318112: [PP1] Move "Block layout" from Structure to Appearance.

I've added #1975064: Add more granular block content permissions as a related issue since it already has a parent issue and added it to the issue summary since it was brought up in #24 got agreed to in #25 but got not added yet there.

#1975064: Add more granular block content permissions was committed, shifting that up in the list, moving #3318549: Rename Custom Block terminology in the admin UI up in the list as it is a higher priority now.

#3318549: Rename Custom Block terminology in the admin UI is in!

Work continues on #2317981: Move block content edit and delete routes under admin/content/block to improve IA for editors and fix breadcrumbs and #3318112: [PP1] Move "Block layout" from Structure to Appearance.

#3318558: Adjust the block terminology in Layout Builder to align with block and block_content changes got unblocked as well now. Left a comment about the current state there and the points left to find consensus on.

Also, #2317981: Move block content edit and delete routes under admin/content/block to improve IA for editors and fix breadcrumbs was committed 🎉

Now to finish off #3318112: [PP1] Move "Block layout" from Structure to Appearance (fingers crossed it can still get into 10.1)

The core ideas project is deprecated.

There is one open child issue here, which is in the core issue queue. By convention we can close issues with one remaining child. So, I am closing this issue.