Improve handling and look of Page, Area and Component edit bars (MAGNOLIA-4308)

[MAGNOLIA-4338] Implement inheritance for areas Created: 25/Oct/11  Updated: 22/Mar/12  Resolved: 30/Nov/11

Status: Closed
Project: Magnolia
Component/s: page editor
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Neutral
Reporter: Andreas Weder Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Inherited content.png    
Issue Links:
relation
is related to MAGNOLIA-4148 Inheritance: Inherited Areas & Compon... Closed
Template:

 Description   

Areas may show content they inherit from a parent page. An inheriting area may allow some of its content to be rearranged, changed or even deleted. It may also offer to add new components.

If an inheriting area can't be changed (it can't be overridden), it actually can't be edited and thus uses a reduced bar to mark its presence (see SCRUM-495).

Whether an inheriting area can be overridden or not is indicated by a small icon on the edit bar. Clicking on the icon changes its state from "inheriting content" to "override inherited content" and vice versa. The icon thus acts both as a status indicator as well as a button. Once an area gets editable, it shows buttons and edit bars according to how it has been configured to behave.

The attached mockup shows both a possible realization of this as well as two examples of overridden areas.


Generated at Mon Feb 12 03:54:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.