The last version of Internet Explorer, version 11, was released on October 17, 2013. This is a very long time ago when taking into account the rapid development of web technologies. These days it is often difficult and time consuming to get modern technologies to work well in this old browser. More and more frameworks are dropping support, and even Microsoft themselves has announced that they will fully drop support for IE in their own services in 2021.
Consequently, we have decided to not include support for IE in the Design Library website.
We strive for a content-cased navigation, with the hierarchical navigation as support.
These are the components that together support our users' ability to navigate:
Users will always be more prone to navigate by clicking their own data, than the navigation provided as site hierarchy.
Use these Figma templates when designing responsive micro frontend pages for common shells: Templates for common shells
Template example with tab navigation
The main navigation of internet banks consists of
This is the landing page of the site. Should give a good overview of the current financial situation and guide users to the items that need attention from this visit. In a further future we may have more than one overview. It might be possible to build own custom pages or projects consisting of widgets and tools for a particular task (i.e. to assist in a complex task like buying a home).
Every site needs a backbone of the hierarchical structure. This gives a sense of structure and makes it easier to find functions related to each other. The main navigation has two levels.
In Nexus, the employee can search for a customer and get the customer's holdings (see the same pages as the customer) in the same navigation structure as the employee. The employee can see several customers at the same time by doing a new search and selecting the customer, then the customer opens in a new tab in the browser.
The shell is responsible for the breadcrumbs and is placed above the H1.
However, support for breadcrumbs is not implemented in all channels yet. If you need breadcrumbs in the meantime, add them to your micro frontend placed under H1 (main header). See guidelines and specifications for Breadcrumbs.
The global functions group features that are available on all pages and are always the same.
The profile of a user is a centralised feature that gives a clear sense of being logged in displaying the users name. Under the profile a number of features kept and may include items like:
Here users are notified about items they need to act upon. Some may feel like nice to know, but it may be important for legal reasons to make sure users see this message.
Looking into the future, it may also hold a feed of everything that happens with your finances and gives you an update that’s easily glanceable just like the updates from Facebook.
The footer is placed at the very bottom of each page and should focus on contact options. For example entry points for contact, feedback and help.