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

[MAGNOLIA-4335] Make (only) top-level area edit bars transparent and hovering Created: 26/Oct/11  Updated: 22/Mar/12  Resolved: 22/Dec/11

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

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 Location of Top-Level Area Bars.png    
Template:
Date of First Response:

 Description   

Top-level area edit bars are are somewhat different from other areas:

  1. They are often less relevant to editors, since they are non-editable (on a typical STK sub page, there are about as many non-editable as editable areas)
  2. They tend to disrupt the layout most, if rendered in-line with the rest of the content (as proposed SCRUM-492), since the higher up you disrupt the layout, the more visible the changes are
  3. They are important as they help visualizing the page structure


I thus suggest to render top-level area edit bars different from all other bars on the page:

  • they are rendered on a different, higher layer (z-level).
  • since they hover above content, they are also made slightly transparent
  • they are rendered using a reduced bar as other non-editable area edit bars (see SCRUM-495)


 Comments   
Comment by Andreas Weder [ 26/Oct/11 ]

Added a comprehensive example of rendering of a page with top-level area edit bars.

Care has to be taken that a top-level area edit bar does not cover the page bar. In the screenshot, I've added the page edit bar on yet a higher layer, which makes the area bars effectively go underneath the page edit bar. This contradicts with SCRUM-494, however, which asks for the page edit bar to be rendered in-line with the rest of the page content.

Comment by Espen Jervidalo [ 22/Dec/11 ]

They are not displayed at all atm.

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