| Uxstatus |
|---|
| revisit | revisit | Not completed yet, missing mockups |
|
Story
If I select a content element on a page I'm currently editing, Magnolia presents me a list of common actions I can execute on it. With these, I can add new elements, edit the element, move or delete it, etc., if I have the necessary rights to do so. I can also retrieve a list of all actions defined on my element, but it's the common actions which are visible by default.
...
Description of desired behavior
| Anchor |
|---|
| Actions Sidebar |
|---|
| Actions Sidebar |
|---|
|
Similar to AdminCentral, in page editing, an
Actions sidebar offers me a list of actions applicable to the currently selected content element. This could be either the page itself, a paragraph or an area.
| Mockup |
|---|
| Actions Sidebar |
|---|
| Actions Sidebar |
|---|
| Version | 5 |
|---|
| 1Name | 4Actions Sidebar |
|---|
|
The sidebar is shown in a column on the right side of the screen (left side on RTL setups) and has three distinctive parts. The header at the top shows the Magnolia logo, but is mainly used to signal notifications for waiting or missed messages such as errors or warnings. Visually, it references the appearance of the header area in AdminCentral and thus seconds to flag the space dedicated to controls and settings.
...
| Mockup |
|---|
| Collapsing the sidebar |
|---|
| Collapsing the sidebar |
|---|
| Version | 11 |
|---|
| Name | Collapsing the sidebar |
|---|
|
Care must be taken to ensure that changing from the expanded view of the sidebar to the collapsed one does not disorient and confuse the user. Use the animations to smoothen the transitions as defined for the Actions Rack and slide the preview up and down instead of abruptly opening and closing it.
| Note |
|---|
|
The following paragraph on message notifications is not final yet, but already captures how notifications will work once multiple message services exist. |
...
