Investigate Designsystemet web components

[mimarz]

Investigate and set the premise of what the Designsystemet web components are going to be (and not).

Make a blog post about our findings and approach

Notes

• State of web components
• Explain why we won't make web components for all components
• Code convention for making web-components
• Testing, linting, formating etc.
• Which components do we see as web-component candidates

[hallvard]

A comment from the side here: As you say, not all elements need be web components, as some don't need the abstraction and encapsulation (of logic and structure) that web components provide. The simple ones can be just HTML + CSS. As a library user, it doesn't really make much difference, since web components look like plain HTML and are supported natively by the browser. So why not just create one version of Designsystemet called browsernative or something similar, and make a note of which components are actually web components. The important point for the developer (library user) is that using this version doesn't imply having to use a specific framework.