Internet Explorer is not supported by Design Library

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.

Luckily, there are modern options in active development. Please use Firefox, Edge or Chrome instead.

Channel taxonomy & page types

There are two groups of pages, aggregated pages and base pages.

Aggregated and base pages

Aggregated pages

Pages on the top of the hierarchy such as start page and theme pages that summarise an area such as savings, liquidity, finance, etc. These pages don't really have content of their own but show snippets of information leading the user to pages further down in the structure based on interest or attention.

Base pages

Pages where we have the real content. The content lives on module-pages, product-pages etc.

Page types

Start page

The startpage is the first view a user is greeted by after having logged on. This page mainly consists of widgets from all sections of the site and covers all/the most important aspects of the users arrangement.

Startpage IB exampel

Startpage IB exampel

Start page exampel IB

Start page exampel IB

 

Theme page

Theme pages are very similar to the start page - the difference is that they holds only widgets of a certain section. Examples might be savings, liquidity, finance, etc.

Theme page example

Theme page example

Theme page example

Theme page example

 

Module page

This is obviously where the module lives. It holds all pieces of information containing to one subject. The module takes up the most space, but under the module widgets might be placed to support the content in the module. Examples might be accounts, funds, loans, liquidity.

Module page example

Module page example

Module page example

Module page example

 

Legacy page

The legacy page is imilar to a module page but with the "module" as an iframed part of an old or external system. This may have implications for responsiveness and how it can interact with the rest of the site.

Please note that pages (from IBF or C&I Online) that are not fully responsive. hold the full page width until the 1920px breakpoint.

Legacy page example for desktop

Legacy page example for desktop

Legacy page example for mobile

Legacy page example for mobile

 

Products and services

Product and services is our store and shows what product SEB can offer you as a customer.

  • In the current internetbank private (IBP), it is basically a site-tree with links to all products.
  • For Business Arena, every service is shown as a product card that leads to a product page.
Product services page example

Product services page example

 

Product page

The product page aims at both selling and explaining the product. For the corporate segment, a template in Figma (design tool) is available.

It is divided into four parts:

  • A header with product name, price and call to action button
  • A short introduction with unique selling points
  • Images that illustrate the product, up to nine images. This section is optional
  • Detailed product information
Product page example

Product page example

 

Internal fields on a customer's page

Sometimes the employee needs to make internal changes (which are not shown to the customer) on a customer's page. Nexus plans to create a template for these internal fields, so that all micro-frontend pages will have the same pattern in the shell. When the template is ready, we'll update it here.

Contact Nexus Channel Manager Robert Skoglund, if you are planning to use internal fields on a customer page.

Subsections

Page last updated

Feedback

Was this helpful?