Contrib.social

Improve the overview of the list of available content types with a layout and layout overrides for its nodes

Open on Drupal.org →
Created on 2 December 2022, almost 2 years ago
Updated 19 April 2024, 6 months ago

Problem/Motivation

During several presentations for the proposed changes in 🌱 [meta] Reorganize Block items in the administration menu Active one problem and key desire in the context of layouts gradually manifested similar to #3325029: Improve the overview of the list of available blocks → which is in the context of blocks (see https://www.drupal.org/project/drupal/issues/3318558#comment-14789485 📌 Adjust the block terminology in Layout Builder to align with block and block_content changes Active ).
When you have a complex site with several content types and quite a few of them have the use layout builder option activated under manage display, and a few even enabled layout overrides on a per node basis for that content type. Problem is if you are new to such a complex site or in case you revisit such a clients site after a several months where the team kept on editing and changing layouts you have no way to know which content type has a general layout and in case layout overrides are activated on a per node basis and no idea which of the nodes of that content type have an actual layout override and which don't have.
The issue spun off a discussion about https://www.drupal.org/project/drupal/issues/3318558#comment-14789485 📌 Adjust the block terminology in Layout Builder to align with block and block_content changes Active (last paragraph) in #3323771: Drupal Usability Meeting 2022-12-02 → . For the record the participants in the usability meeting were @antoniya, @aaronmchale, @benjifisher, @rkoller, and @simohell.

Steps to reproduce

  • create two new content types (music and art)
  • create nodes for the article, basic page, music, and art content types with devel.
  • go to /admin/structure/types/manage/art/display and admin/structure/types/manage/article/display and check both box layout options.
  • create a general layout for the article, music, and art content type.
  • get into a few of its nodes created with devel and create a few layout overrides.
  • now let someone else access the site and quickly find out which content types and which nodes have dedicated layouts.

Proposed resolution

  • The initial idea during the discussion with meetup groups was to create a list view similar to the custom block library listing all available layouts in the system (the page might be added as a child of the appearance page alongside the block layout page being moved to there as well - see the plan in 📌 [PP1] Move "Block layout" from Structure to Appearance Postponed ). that way you would be able to see for one which content types and nodes have a layout and at the same time you would be able to get directly to the layout page of the content type and or node in question. you would have an overview as well as an easier direct access with less number of clicks necessary.
  • During the UX meeting there was a doubt if it would be a good idea to have a list view with all layouts and layout overrides even though the general need for some sort of overview was recognized. the fear was that such a page might be too overwhelming. one suggestion was to add a filter option on /admin/content to illustrate nodes that have a custom layout.

We've agreed that the topic is definitely in the follow up territory to the meta issue ( 🌱 [meta] Reorganize Block items in the administration menu Active ), worth to pursue and discuss, but nothing that should derail the meta. Therefore i've added the issue only as related and assigned it also to the component layout_builder.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

✨ Feature request
Status

Active

Version

11.0 🔥

Component
Layout builder  →

Last updated about 7 hours ago

Created by

🇩🇪Germany rkoller Nürnberg, Germany

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 6 months ago →
    🇳🇿New Zealand danielveza Brisbane, AU

    This has been open for close to 18 months with no additional thoughts given.

    I believe this could be built with views integration based on entities layout_builder__layout field (This may exist already). I'm -1 on having this as part of core, I think this would be a great candidate for a contrib project that can be required by the sites that want it.

    Keeping it open but marking as postponed for others to give their thoughts

  • Status changed to Active 6 months ago
  • Comment 6 months ago →
    🇬🇧United Kingdom AaronMcHale Edinburgh, Scotland

    Just because an issue has been open for a long time doesn't mean it needs to be postponed, generally issues should only be postponed if there's an actual need to block the issue on another issue or an external factor preventing it from being progressed. Marking an issue as postponed only reduces any potential for engagement on it.

    That said, I don't have a strong opinion either way on whether this should be done in core or not. This issue was opened following a Drupal Usability Group meeting, and during the meeting it was identified that there is a user need for this.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024