PR for iteration on fine-tailoring components overview at https://github.com/wikimedia/WikimediaUI-Style-Guide/pull/224

Related: T236119: Slider: Add Slider `input type="range"` component to Codex

Current state of Git repo:
From the basic components defined to be for roll-out necessary, toggle switches and tags are currently still to be added.

The repo has finally deployed after ~2weeks being stuck in T235677.

From conversation with @cmadeo, she reviewed exemplified Checkboxes:

• Use clearer in-image labels for checkboxes “selected”/“unselected” vs “neutral point”
• Does “Designing” make sense in the current structure when it's a repetition of introductory paragraph?

From my POV we also would like to provide an overview of some of the main design decisions without getting to abstract in order to share openly the design, internationalization, usability and accessibility thoughts behind…

From conversation with @alexhollender, he reviewed exemplified Links:

• In the look & feel of components, interactivity is lacking somewhat

Responded, that we aim to pursue being template and leaving interactivity mostly to the implementation demos.
Alex would yet consider usage of some motion, even if it's just an animated Gif representation.

• Is indentation of the components images best way? With added interactivity (see above) it would become more clear, now image example could be confusing to some.

• “Using” section would work better when compared to other components, exemplified on when to use links vs buttons…

That's a rightful argument, and has been part of the original intention for “Using”. We should further strengthen this idea behind the section.

• Mobile vs desktop in imagery, which of all of this is catered/meant for?

Point taken, the integration of :hover states is clearly desktop targeted. No clear idea how to better cater the difference without massive maintenance overhead right now.