Description
Layout is the arrangement of visual objects within the interface. The layout should reflect the structure of the content and patterns of usage, helping the user to navigate large amounts of information.
Consistent Verint layouts are as important as graphical styling.
Types
Type | Description | Layout | Example |
Used by default for Verint applications. For more information, see VerinTop Top Navigation. |  |  | |
Used for Verint applications with larger navigation menus. For more information, see VerinTop Left Navigation. |  |  | |
Web layout | For Verint web pages, such as in Verint Connect. Contact the UX team for more information. |  |  |
Arrangement
Make sure there’s a natural flow between the elements on the page. Where there is a natural hierarchy between objects, it is recommended that they are arranged from top to bottom, left to right. For example:
the page is identified in the header area.
a list of available parameters for the content is shown on the left.
the main content is available in the central workspace.
additional details on selected elements within the main content are shown on the right.
Structure
Layouts consist of:
VerinTop
Ribbon (optional, top navigation layout only)
Header area
Main workspace
Left pane, containing either:
Left navigation (left navigation layout only)
Filter Pane (optional, top navigation layout only)
Right Details Pane (optional)
VerinTop
The VerinTop is a mandatory consistent pattern appearing at the top of all Verint layouts. VerinTop:
is in a fixed position at the top of the page.
contains either:
navigation within the main product hierarchy (top navigation layout), or,
Instances (optional, left navigation layout).
See the VerinTop page for more information.
Ribbon
For Top Navigation Layout only.
Ribbon should be used where there are a lot of controls for the main workspace. The ribbon should:
be fixed underneath the VertinTop.
be the full width of the page.
be collapsible.
For more information, see Ribbon.
Header area
The header area contains information which relates to the whole page.
Structure
The header area can include multiple components, including:
Page title (mandatory)
Header text, such as a page description
Chicklets for applied filters
Tabs to change the view within the main workspace.
Tools such as Search or an Action Menu.
Other page metadata, such as a status indicator.
Placement and Positioning
The header is positioned at the top of the page, directly underneath the VerinTop.
The height of the header area may vary, depending on which components are included.
The header area should be the full width of the page, with the exception of the left pane. It may optionally stretch above the details pane.
Breadcrumbs, header text, and tabs should be aligned to the left-hand side of the header area.
The action menu should be aligned to the right-hand side.
Main workspace
The main workspace contains the primary content, so should be central and granted the most space within the layout.
Structure
The main workspace may include multiple sections using Widgets. Widgets may be fixed or managed by the user within a dashboard.
Each widget should be uniquely identifiable with its own discrete controls. For more information, see Widgets.
The workspace content may consist of:
Textual and graphical content
Placement and Positioning
The main workspace should be central within the layout.
Content
Make sure each section within the main workspace is distinct and identifiable.
The content of the main workspace should be fluid, adapting to the size of the available area, even as it changes during use. Where widgets are used, the size of the widgets may adapt, and the contained content should fluidly respond. - move to responsive section.
Left Pane
The left pane may consist of either:
Left Navigation pane, containing a collapsible navigation menu.
Filter Pane, used when there are options to refine what is shown in the main workspace.
Placement and Positioning
The left pane should:
stick to the left side of the page, beside the main workspace.
have a fixed width.
always fills the vertical space, from beneath the VerinTop to the bottom of the page.
There should be no additional elements between the left pane and the main workspace.
Right Details Pane
The right-hand details pane should be used to present information and actions relating to selected items within the main content, or additional content related to the main workspace.
For full details, see Details Pane.
Placement and Positioning
The details pane should:
stick to the right side of the page, beside the main workspace.
have a fixed width.
fill the vertical space to the bottom of the page. The top of the details pane should start from either:
a few pixels beneath the VerinTop, to align with the top element in the header area, or
from a few pixels beneath full-width header areas.
Interaction
The layout may not have a whole-page scroll. Each individual pane or widget may have its own internal vertical scroll where necessary.
The right and left panes are collapsible, depending on the layout width. See individual pane designs for
Best practices
Make sure there’s a natural flow between elements on the page, from top to bottom, left to right.
Prioritise the most important elements to facilitate user decisions.
Form associations between related elements by keeping them in close proximity and using similar styling.
Keep controls in the same area as the content they manage.
Be aware of common scanning patterns, such as the F pattern, where users scan across the top and down the side of the content to find what they’re looking for.
Use:
fluid responsive design, to ensure the layout works at all screen sizes, across devices and browsers.
headers for each area within the layout to make sure they are easily identifiable.
consistent spacing between elements.
color sparingly, only for the primary information and calls to action.
the same layout for pages with similar content.
Don’t use:
controls in the header area which don’t affect the entire main workspace.
Responsive design
Verint products should dynamically respond to the user’s screen size, platform, and orientation, supporting all devices down to the common tablet size (960px width).
For more information, see the general Responsive Design guidelines.
Where there is not enough space to display the full layout, the main workspace should be prioritised. Other areas within the layout may be collapsed or minimised, including the left and right panes.
Where space is severely limited, it is acceptable to remove auxiliary functionality, but this should be avoided where possible.
Using a mobile-first approach can make layout design and implementation easier.The layout of content within the main workspace should dynamically respond to the size of the available area. This may change due to the state of collapsible panes as well as screen size.
When the screen width is changed, anchored panes and components should remain fixed to the left- or right-hand side.
The size and spacing of individual components and fixed panes (such as the Filter Pane and Details Pane) should not change as the layout dynamically responds.
Where there is no longer space for a component, see the recommended responsive design for the individual component.
Layout responsive design example
Wide | Standard | Tablet | Mobile |
 |  |  |  |