As an Umami user
I want layout builder to work on the Umami provided content
So I can have a great site building experience using Drupal
So I can see how powerful Drupal is OOTB

Explanation of the problem or need and its impact

When you install the Umami profile on a fresh D8 application, the Layout Builder and Layout Discovery modules are enabled by default. This, I assume, is to ensure that new-to-Drupal users have a good experience and see how powerful Drupal is. Unfortunately, Umami's OOTB configuration does not provide the ideal layout builder experience.

When you install Umami, the current layout builder experience is lacking/confusing. For example, only content of type Article can have its layout changed. It is not reasonable to expect users to notice that Article's layout can be changed (via the "layout" tab) but not Basic Page and Recipe content. In reality, it is much more likely that a user will attempt to change the layout of Basic Page content such as the home page and about page first.

If Umami is meant to be a quick starting point to show what Drupal is capable of, then layout builder should be fully enabled on all content by default. To provide this experience, the following changes need to be made:

  1. The "Full content" display mode needs to be enabled on each content type (missing from Basic Page)
  2. The "Use Layout Builder" and "Allow each content item to have its layout customized." options under "Layout Options" need to be enabled on the "Full content" display mode on each content type (missing from Basic Page and Article content types)

That's it! With these two changes, layout builder will be available to Umami users out of the box.

CommentFileSizeAuthor
#7 Screenshot 2023-08-17 at 2.29.50 PM.png569.49 KByash.rode
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hoff331 created an issue. See original summary.

hoff331’s picture

The config that changed after making the recommended changes:

core.entity_view_display.node.page.full:

uuid: 61107289-aa34-4a06-b6f3-42fec98787f6
langcode: en
status: true
dependencies:
  config:
    - core.entity_view_mode.node.full
    - field.field.node.page.body
    - node.type.page
  module:
    - layout_builder
    - text
    - user
third_party_settings:
  layout_builder:
    allow_custom: true
    enabled: true
    sections:
      -
        layout_id: layout_onecol
        layout_settings: {  }
        components:
          3e15d15a-8454-455b-bf62-45f29b0cae94:
            uuid: 3e15d15a-8454-455b-bf62-45f29b0cae94
            region: content
            configuration:
              label_display: '0'
              context_mapping:
                entity: layout_builder.entity
              id: 'field_block:node:page:body'
              formatter:
                label: hidden
                type: text_default
                settings: {  }
                third_party_settings: {  }
            additional: {  }
            weight: 0
          bce67b72-9b3f-4861-a2b1-0ff73491661e:
            uuid: bce67b72-9b3f-4861-a2b1-0ff73491661e
            region: content
            configuration:
              label_display: '0'
              context_mapping:
                entity: layout_builder.entity
              id: 'extra_field_block:node:page:links'
            additional: {  }
            weight: 1
        third_party_settings: {  }
_core:
  default_config_hash: anjk6k7WgGroZenWdvap2K6hdEbWKRXfL8Phxq_qxPs
id: node.page.full
targetEntityType: node
bundle: page
mode: full
content:
  body:
    label: hidden
    type: text_default
    weight: 100
    region: content
    settings: {  }
    third_party_settings: {  }
  links:
    weight: 101
    region: content
    settings: {  }
    third_party_settings: {  }
hidden:
  content_moderation_control: true
  langcode: true

field.field.node.article.layout_builder__layout

uuid: 59e4e017-b2a9-4aac-8081-1d381b2f331a
langcode: en
status: true
dependencies:
  config:
    - field.storage.node.layout_builder__layout
    - node.type.article
  module:
    - layout_builder
id: node.article.layout_builder__layout
field_name: layout_builder__layout
entity_type: node
bundle: article
label: Layout
description: ''
required: false
translatable: false
default_value: {  }
default_value_callback: ''
settings: {  }
field_type: layout_section

field.field.node.page.layout_builder__layout

uuid: 30d8c24f-6b18-42d7-a6c9-135da15be5cd
langcode: en
status: true
dependencies:
  config:
    - field.storage.node.layout_builder__layout
    - node.type.page
  module:
    - layout_builder
id: node.page.layout_builder__layout
field_name: layout_builder__layout
entity_type: node
bundle: page
label: Layout
description: ''
required: false
translatable: false
default_value: {  }
default_value_callback: ''
settings: {  }
field_type: layout_section
hoff331’s picture

Issue summary: View changes
hoff331’s picture

Issue summary: View changes
hoff331’s picture

Issue summary: View changes
yash.rode’s picture

Assigned: Unassigned » yash.rode
Status: Active » Needs work

Investigating this.

yash.rode’s picture

Assigned: yash.rode » Unassigned
Issue summary: View changes
Status: Needs work » Needs review
FileSize
569.49 KB

I think we can close this issue as, both of the problems mentioned

  1. The "Full content" display mode needs to be enabled on each content type (missing from Basic Page)
  2. The "Use Layout Builder" and "Allow each content item to have its layout customized." options under "Layout Options" need to be enabled on the "Full content" display mode on each content type (missing from Basic Page and Article content types)

are already fixed in Drupal 11.x or some older version.

Proof:

markconroy’s picture

As an Umami maintainer, I don't think this feature request will be accepted.

Umami shows lots of features of Drupal core, layout builder is one of them. However, we also want to show that there are other ways to manage layout, such as templates and also the old fashioned "Manage display" page.

markconroy’s picture

Status: Needs review » Closed (works as designed)