Decide whether to convert standard elements into custom components

[oliverschuerch]

There are some pros and cons, why we should build Custom-Components for standard HTML-Elements, such as button, etc.

Pros:

• We can define a standard behaviour in the Custom-Component.
• DEVs do not need to know every CSS-Class, internal HTML-Structures or whether attributes can be combined or not.
• We can provide a more consistence User Experience between all the Components.
• Styles are capsulated.
• Some JS logic can be abstracted away.

Cons:

• It can be hard to build a Custom-Component which reflects a standard HTML-Element.
  • There are a lot of specs to pay attention on to provide a correct Component (W3C, a11y, etc.).
  • We need to find a solution to provide some kind of Attribute heritation.
  • We need to find a solution to make events work correctly with this Components.
  • We need to find a solution to make ScreenReaders work correctly with this Components.
• The added value for devs may be too low.
• It is possible, that such Components are to static/not dynamic enough for our DEVs.

[gfellerph]

@oliverschuerch, I will provide some insights from the Successful Design Systems Course. This feels like a good candidate for an RFC just to document the descision.

[gfellerph]

Started a discussion #1224

[gfellerph]

According to discussion #1224, we strive for a solution where we have basic html + css components as well as web-components variants that share the same basic styles.