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.
There are two groups of pages, aggregated pages and base 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.
Pages where we have the real content. The content lives on module-pages, product-pages etc.
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.
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.
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.
For example: accounts, funds, loans, liquidity.
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.
Desktop and mobile
Product offering is our store and shows what product SEB can offer you as a customer. This page is not specified at all yet. In the current internetbank it is basically a site-tree with links to all products.
The product page aims at both selling and explaining the product. It is divided into sections, starting from the quick selling points and continues with sections for emotional, educational, details, frequently asked questions or whatever details are needed to clarify the product.
Almost every section holds a call-to-action enabling the user to buy/get the product.
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.