You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Overview

Critique of the current design

The current design has reached its limits in a number of areas - a separate page describes these problems in more detail. But it has also set landmarks: the green edit bars act like markers for editable elements and they work very well on touch devices. The switch to turn off these bars provides a user with the perfect preview of the page with all its features fully working. In addition, the site can be browsed both in preview and editing mode, which makes it very intuitive to work on a number of pages or sections an editor may be responsible for.

The redesign of the current, preview-based editing into the Visual Page Editing of Magnolia 5 aims at providing a solution for all described problems while retaining all qualities of the existing implementation.

The new interface

The standard interface of Visual Page Editing shows two main sections. Most of the screen is occupied by a preview of the page with the well-known green bars marking the editable paragraphs. A newly introduced toolbox on the right of the screen presents all actions and options applicable to the currently selected item or the page as a whole. The toolbox improves the overall visibility of actions and options by providing them with both a clear location on screen and enough space to present their interface. It introduces flexibility and scalability to support current and future modules wishing to add complementary functions to page editing.

The new visual page editing is still targeting mouse input, but has been crafted with touch devices in mind. While you can use this interface with a keyboard, Page Structure Editing has been specifically optimized for keyboard input and thus should be the preferred way to edit a page using keys only.


Please configure the Balsamiq Wireframes macro and select the wireframe to show. Learn more

Concepts

Area editing

Visual page editing in Magnolia 5 keeps the edit bars introduced in earlier versions, but solves the cloud of bars by introducing Area Editing. The areas of a web page as defined by the web designer and introduced in Magnolia with STK templating are an excellent starting point to reduce the number of edit bars visible at any one time.

Please refer to the separate page on Area Editing for an in-depth description of this concept.

The Toolbox

Magnolia 5 adds a toolbox to the page editing interface. It

  • it shows all applicable actions available to the logged-in user and defined on the currently selected paragraph, selected area or on the page ifself
  • it offers access to global functions such as undo/redo and copy & paste
  • it hosts a set of options of the currently selected paragraph, selected area or the page itself
  • it contains a small panel denoting the name of the instance as well as the logged-in user
  • it provides more flexibility and scalability for actions and options
  • it shows notifications and provides access to the list of system messages

The toolbox replaces the edit bar dedicated to the page, which was shown at the top in preview-based editing in earlier Magnolia versions. The page properties are accessed using a regular page action. Page options like a language selector or information on page links have been extended and moved to the options rack (see definition below). The button to return to AdminCentral has been replaced with a button to leave editing in the Toolbox, which is also where the "Preview" button was moved to.

Racks and Units

A rack is basically an enclosure for mounting multiple modules. In Magnolia 5, a rack is a container for a basically arbitrary (but usually small) number of units. Each unit collects a number of UI elements logically belonging together, such as a language selector or an element representing the translation status of the current page.

The goals of the racks and units concepts are:

  • to offer a great overview of various aspects of an element while keeping the interface simple
  • to provide a scalable UI solution for adding functionality to pages, paragraphs, areas

A unit may either use a single-state or a two-state interface. If a unit can provide a short overview of its core settings, but needs more space to show all values, it is dubbed an expanding unit and uses the two-state interface offering both a collapsed and an expanded view. In the expanded view, the unit takes over most of the space available in the rack and thus has plenty of space available to show its data. In the collapsed view, only the brief overview fits in. If a unit only needs one interface to show its settings it is called a uniform unit and uses a single-state interface using the collapsed view only.

The toolbar
Working with a paragraph or the page

The toolbox features a two-level control at the top for the selection of a target and a rack. The target may be either a selected paragraph or area or the page itself. The targets you may choose depend on which elements are currently selected on the page, if any. If a paragraph is selected, the target can be either this paragraph or the page as a whole. If no element is selected, then the page is the only valid target left.

Once you selected a target, racks become available allowing you to choose either actions or options related to your target.

Note that while this concept may sound complicated, its day-to-day use actually isn't. If you select a paragraph on the page, the target selector is automatically switched to "paragraph". The same holds if you select an area. If you deselect any element, the target selector switches to "page". The only time you have to manually switch it is when you've selected a paragraph, but would like to switch back to work on the page level to e.g. activate the page.

Actions and Options rack
Uniform and expanding units
More space in a rack
  • No labels