For many page layouts, section layouts often need to nested to achieve the required layout designs. Right now layout builder doesn't make this easy because layout sections cannot be nested. This requires developers and site builders to incorporate some other way to added these nested grids, such as a grid paragraph type, or using the standard block UI for adding sidebar blocks.
For instance, one common page layout is having a left and right sidebar section and middle content section. The left sidebar section might have a menu block, while the right might have related block such as related content/links, forms, ads, or other information complementary to the main content. Within the middle content section, content editors often still need to place content in multi-column grids. Some examples include: placing an image and text in a 2 column grid (often called a media object), a grid of cards or photos, multi-column lists, etc.
Allowing layout builder sections to be nested would greatly increase the flexibility and functionality to easily implement even the most complex of layouts.
Extend layout builder sections functionality to allow them to nested.
Agree on an approach and implement.
Layout builder UI will be to be adjusted to properly accommodate nested sections.
Unknown.
Unknown.
Active
11.0 🔥
Last updated
Blocks and Layouts Initiative. See the #2811175 Add layouts to Drupal issue.
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Almost 2 years further, is there by chance any update on this? Any way to fix this instead using another module like layoutcomponents?
Tagging for https://www.w3.org/WAI/WCAG20/Understanding/focus-order which is the most likely error which would be introduced by this feature.