Add and configure master displays

Created on 15 November 2012, almost 13 years ago

Updated 5 September 2025, about 15 hours ago

This is a sub-issue of 🌱 [META] Decouple layouts from themes Active .

Problem/motivation

With all page components hopefully converted to blocks (such as page title, primary menus, secondary menus, etc) *and* the proposed possibility to create landing pages with separate block setup / placement / configuration, we need a way to control master layouts where the common elements are placed, so when you create a page with a layout, you don't need to start over and place all the common elements all over again.

Proposed solution

Ideally we would have a way to create multiple master layouts that can be used to create pages with different block setup, however, for the pre-feature freeze scope, it seems possible to only support master front end and master backend layouts, where all pages are derived from this layout. Also while we call these layouts on the frontend, the backend implementation calls them displays.

Designs for proposed solution

Listing of two specific layouts possible:

Editing of the layout:

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

other

Created by

🇭🇺Hungary Gábor Hojtsy Hungary

Live updates comments and jobs are added and updated live.

JavaScript

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

Needs issue summary update
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

layouts

Spark

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment about 15 hours ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024