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.
Introductions to what you might need to know to create a unified experience, in a certain context. This chapter is being worked on at the moment, stay tuned.
We have several common shells that targets a specific customer or user. This section lists them and gives a quick overview.
The local adaptions and who you should contact for each current channel.
This section is about how to think about grid and responsiveness when designing for our common shells.
We strive for a content-cased navigation, with the hierarchical navigation as support.
There are two groups of pages, aggregated pages and base pages.
The content area is divided into three zones that contain different types of content depending on its function.
Sometimes errors will occur and we need to handle them uniformly, and sometimes escalate them to incidents or close the function with a stop page.
When you are going to create a micro-frontend page, you need know what guidelines there are for an internal or/and an external shell.
When we talk about hybrid design, we talk about web being experienced through our native apps.
With hybrid experiences come challenges but also opportunities. Challenges as how to meet the users' expectations of the platform and opportunities su...
Design principles for web with support for hybrid app
The differences between dark mode in hybrid and native
What you need to know to create an experience in public web sites.