Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Concepts/Admin Service UI

Introduction

The point of this article is to specify an optimized Admin UI with focus on usability and flexibility.

Current version: 0.1

General Structure

Admin service ui schema.png

Header area contains the application logo and title (as link to dashboard), information about the log in state (username acting as link to profile site) and log out link as well as a quick access dropdown for the most important application functions.

PopIn area for pagespecific actions is only diplayed on top of the page (fixed position) whether the section for pagespecific actions below header scrolled out of visible browser area. PopIn area contains the same elements as the area below header. Actions can be filtering options as well as buttons or others.

Notification area is only shown if notifications are available. Notifications can be messages like "saving successfull" or "please note that there are unsaved changes". Errors or more important messages are not displayed here but in dialog boxes interrupting the accessability of the application functions until the user confirmed attention of them.

Page actions, notifications and site content as one are seen as working area. The working area is flexible in width. That means if main menu is collapsed the working area enlarges automatically. Due to this it must be realized in a fluid design.

The Section Title reflects the shown content on the site. Normally it is the same term as used as label in the navigation.

Navigation Concept

Main Navigation is positioned at the left of the application. It guarantees access to all parts of the site through a collapsable menu. Its depth should not exceed two levels i.e. main level with one sub level. Collapsable means it is minimizeable in two ways.

The first concept is that it is possible to fade in and fade out sub menus similar to a treeview.

Main menu itself is collapsable i.e. it can be reduced to the icon of any entry. For that purpose every icon must be explaining the object of the menu entry, it must be associatively. In that case sub menus are displayed in flyouts.

PopIn

As mentioned before there is a so called "PopIn" area which is displayed if there are page specific actions (like saving buttons or filters) and these actions are out of accessibility due to scrolling down in the browser.

Back to the top