This new layout is Sugar's main component that hosts overall Menu options structure in the newly redesigned Home Page.
It has been designed to group functionalities in layouts, where each layout/group is separated by a line/divisor within sidebar-nav definition.
Natively on 12.3, Sugar is shipping 4 layouts:
For the sake of simplicity, we’re grouping 2 layouts in this image.
|
|
Quick Create view has been redesigned and presents the modules on click. Note this view does not require secondary-action as others with submenu. |
|
Each item in the menu contains a set of submenus providing the user extra options prior to accessing the functionality (such as header submenus) | |
This layout group brings a scrollable modules list (now called sidebar-nav-item-module).
|
|
This layout group is where Sugar’s footer now resides.
|
Actions
Primary Action
Primary actions are triggered by the click of a button on the sidebar-nav's
views. By default if a route
property is provided in the view object in the layout metadata, the Primary Action will be a link to the route provided. For example:
$viewdefs[...] = [ 'layout' => [ 'type' => 'sidebar-nav-item-group', 'name' => 'sidebar-nav-item-group-bottom', 'css_class' => 'flex-grow-0 flex-shrink-0', 'components' => [ [ 'view' => [ 'name' => 'footer-greet-button', 'type' => '<some-custom-view>', 'route' => '#Accounts', ... ], ], ], ], ];
Otherwise, if you're using a custom view and the controller has a primaryActionOnClick
method defined, that will be used in addition to the route
property.
Secondary Action
TODO update
With the introduction of the sidebar-nav-item component, we’re now introducing secondary actions. These appear by way of a kebab menu when hovering on the sidebar-nav-item
container to which they are added. It can be configured similar to a Primary Action.