Page History

Menu menu described here might still be used, but dev on hold for now

Story

There's a single entry point to all

Story

The left sidebar provides me access to all of my work: the content I have access to, my personal messages and settings as well as , Magnolia configuration settings and tools .These three areas have separate menus, each offering menu and sub menu items as well as technical data such a message logs. This single entry point acts like a menu and offers areas and sub menus for accessing various data sets and functions.

Only one of these menus is visible at once. I can however switch freely between areas and menu items without loosing context. If I e.g. work on assets, then switch to my personal work area to moderate a number of new forum entries, then switch back to the asset browser again, I'm returned to the exact same point where I left of.

Description of desired behavior

The three work areas each have their own top-level tab and menu structure. This brings some structure to the list of menu items and improves orientation: content is separated from personal elements - the profile, personal messages and settings - and instance-level configuration and tools.

If a menu item contains sub menu items, these are hidden at first. If you select the parent item, the sub menu items slide open while possibly already visible sub menu items of another menu item slide close - only one menu item may show its sub menu items at any point in time.

The menu of a single work area is further sub-divided into groups where useful. Access AdminCentral uses a classical menu for providing this single entry point. In order to improve orientation, menu items can be grouped into sets of items logically belonging together. As an example, access to actual content such as pages, assets, documents and structured data is visual visually separated from access to content-related functionality such as A-B testing and statistics. Likewise, ; server and module configuration, templates and security settings are separated from tools and apps such as the Magnolia Store. Groups Menu groups could actually be labelled labeled to improve understanding and clarity, but the current design does not yet foresee that.

If a menu item contains sub menu items, these are hidden at first. If you select the parent item, the sub menu items slide open while possibly already visible sub menu items of another menu item slide close - only one Note that the above rule that only a single menu item may show its sub menu items at any point in time. Note that this is actually applicable across menu groups. If e.g. Configuration->Server,Modules >Modules is open and selected, and you switch to Security, the Configuration menu closes.

Preservation of context

If you switch between menu items and sub menu items of the same or of different work areas, the state of the connected workspace is preserved. This allows to e.g. work on the site structure of one site, then change a template, then go back to the site structure and continue to work.

In order to guarantee the consistency of a workspace, the following set of rules must always hold true (please refer to the conceptual overview of AdminCentral to help understanding the following):

• a workspace is updated with changes made in another workspace, even if it currently not visible. Alternatively, a workspace is updated, before becoming visible again.
• all settings of a workspace such as the state of its controls (asset type tabs, view selection, sorting and grouping options) is preserved and re-applied if a workspace is updated
• likewise, the currently focused item and all selected items must remain focused and selected.
• the set of items shown in the central view area of a workspace must be current and should reflect all changes made in a different workspace.

In case a change applied in another workspace causes a conflict with the preserved state of another workspace, these rules are used to resolve it:

• if the focus has become invalid, it is either removed or moved to the default item of a view
• if the selection of an object has become invalid, it is removed. Additional selected elements stay selected.
• if the set of items shown in the central view area of a workspace is large and only an excerpt of it is shown, the relative position of the scrollbar in regards to the total number of items should remain the same before and after an update. If this doesn't make sense, the excerpt should at least show the first selected item. If no item is selected, it show the item, which currently has the focus. If no item has the focus, the view may jump back to the top of the set of items.

...

find yourself at the exact same spot in the page tree.

For further details about this topic as well as necessary limits that have been set, please refer to Preservation of context.

Notifications

All menu items connected to messaging or system components which may get updated may show a visually distinctive badge listing the total number of notifications of their type, which have arrived and not yet been viewed by the logged in user. All emphasizing visual elements are removed, if the user reads the new messages or marks them as read. Once the total count of new messages reaches zero, a corresponding badge on a menu item is removed.

Typical menus

The following examples show how the current menu items would typically be grouped for Magnolia 5. Note that the menu items available will likely be different.