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.
A module resides in a page and contains all information of a certain subject that might be visually represented as a multiple tables, graphs or even a form. It could be part of a microsite/SPA or act as its own placeholder.
A module gives the user a complete overview of all information available for a specific area.
Since a module holds everything about a certain subject, it may need to split the information on multiple levels. This leads to a need for the module to keep it’s own navigation for the different views.
A typical setup may include:
All functions related to the module, such as print/import/export are found in the page header. Content within the module is responsible to make its own actions accessible within its context. Such actions could be inline search, filtering and affecting a table or graph layout.
Please note that the module is not responsible of what columns are shown in a table or how a graph is visually represented. The same applies for search and grouping of items. Those functions should be part of the actual table or graph content.
Differentiating a module from a widget is accomplished by having all the module content in a single card* and not divided into several smaller ones as used by widgets.
*A module is contained in a card when the zone 3 content is docked to the right side instead of being below zone 2. Visit the breakpoint section for more details.