...

Type	Description	Layout	Example
/wiki/spaces/UserExp/pages/3159884063	Used by default for Verint applications. For more information, see VerinTop Top Navigation.	Image RemovedImage Added
/wiki/spaces/UserExp/pages/3159720340	Used for Verint applications with larger navigation menus. For more information, see VerinTop Left Navigation.
Web layout	For Verint web pages, such as Verint Connect. Contact the UX team for more information.

...

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)

...

See the VerinTop page for more information.

...

Ribbon

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.

Note: the ribbon may not be used in conjunction with left navigation.

For more information, see Ribbon.

Header area

The header area contains information which relates to the whole page.

...

• Breadcrumbs

• Page title (mandatory)

• Header text, such as a page description

• Chicklets for applied filters

• Tabs which 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 main workspace contains the primary content, so should be central and granted the most space within the layout.

...

Placement and Positioning

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.should be central within the layout.

Content

The workspace content may consist of:

• Textual and graphical content

• Data Tables

• Forms

• Data Visualisations

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.

...

• Widget dashboards

Workspace sections

The layout of sections should also have a clear hierarchy, ordered left-to-right, top-to-bottom.

Each section should have:

• a header, to identify its purpose

• any required discrete controls

The spacing between each section should be consistent across the workspace.

Behaviour

Section content may be static or interactive.

Where relevant, sections may have an expanded state, for example in a Popup or separate page, to show the content in a larger space.

The layout of the content within each section should respond to its width. This may include changing text, graphics, table, and spacing sizes.

Sections should be of a fixed size or responsive to their content, but not be adjustable by the user. Is this true? Should users be able to (optionally) make a section full size etc.?

Left Pane

The left pane consists of one of the following:

...

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.

...

• 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.

• The content of the main workspace should be fluid, dynamically adapting to the size of the available area, even as it changes during use. The available space may change due to the state of collapsible panes as well as screen size.

• Where

  widgets are used, the size of the widgets may adapt and each one’s content should fluidly respond

  sections are used within the main workspace:

  • as the workspace width changes so should the widths of the individual sections within it.

  • workspace breakpoints may be added, where the proportion of the width that each section uses is automatically increased. When the width of the workspace is increased again, the original proportions for each section should be restored.

  • there should be a minimum-width workspace breakpoint, below which all sections will be shown at full width, regardless of their original size.

  • the spacing between sections may be reduced at each breakpoint.

• 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.

• 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.

• See the recommended responsive design for individual components, where necessary.

...

Example screens

Top navigation layout

Details panel in AV example goes right to the top?

Left navigation layout

More left nav examples?

Left icon tabs in Details panel isn’t a documented use…