You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -9,7 +9,9 @@ import {Mermaid} from '@site/src/components/Mermaid';
9
9
</KolAlert>
10
10
11
11
<p>
12
-
The unique feature of <KoliBri /> is the <strong>reference implementation</strong> of components that are <strong>semantically W3C- and WCAG-compliant</strong> from the ground up and thus <strong>completely accessible</strong> regarding assistive support. All components are implemented as <KolLink_label="Web Components"_href="https://developer.mozilla.org/en-US/docs/Web/Web_Components"_target="_blank" />
12
+
The unique feature of <KoliBri/> is the <strong>reference implementation</strong> of components that are <strong>semantically W3C- and
13
+
WCAG-compliant</strong> from the ground up and thus <strong>completely accessible</strong> regarding assistive support. All components are implemented
14
+
as <KolLink_label="Web Components"_href="https://developer.mozilla.org/en-US/docs/Web/Web_Components"_target="_blank"/>
13
15
and are therefore reusable in all web-based projects. In the following figure, these components are represented by the gray-dashed shapes in the center.
14
16
</p>
15
17
<p>
@@ -24,15 +26,24 @@ import {Mermaid} from '@site/src/components/Mermaid';
24
26
/>
25
27
26
28
<p>
27
-
In the first release (v1.0) <KoliBri /> had directly implemented the individualization of the standard design using
(<KolLink_label="Design-Tokens"_href="https://uxdesign.cc/design-tokens-for-dummies-8acebf010d71"_target="_blank" />, <KolLink_label="Tailwind CSS"_href="https://tailwindcss.com"_target="_blank" />). With the implementation of further themes, however, we have found that we would have to introduce more and more CSS-Properties to be able to implement the flexibility for the desired design/UX (Corporate Design/Style guide). In
30
-
case of doubt, a separate property would have to be provided for each customizability. The example of the <KolLink_label="MUI-Button CSS"_href="https://mui.com/material-ui/api/button/#css"_target="_blank" /> shows well how the CSS properties (design tokens) become more and more.
29
+
In the first release (v1.0) <KoliBri/> had directly implemented the individualization of the standard design using
implementation of further themes, however, we have found that we would have to introduce more and more CSS-Properties to be able to implement the flexibility
36
+
for the desired design/UX (Corporate Design/Style guide). In
37
+
case of doubt, a separate property would have to be provided for each customizability. The example of the <KolLink_label="MUI-Button CSS"
2. We have completely decoupled the whole CSS from the components (like <KolLink_label="Styled-Components"_href="https://styled-components.com"_target="_blank" />).
45
+
2. We have completely decoupled the whole CSS from the components (like <KolLink_label="Styled-Components"_href="https://styled-components.com"
46
+
_target="_blank"/>).
36
47
</strong>
37
48
</KolIndentedText>
38
49
</p>
@@ -93,7 +104,7 @@ stateDiagram-v2
93
104
<p>
94
105
For example, the UI/UX team specifies the components of their design system with Figma. When the specification is
95
106
transferred to implementation, the design is “transferred” to the basic components in the form of pure CSS using the
96
-
<KolLink_label="KoliBri-Designer"_href="/en/docs/concepts/styling/designer"/>. If customizability is desired in your
107
+
<KolLink_label="KoliBri-Designer"_href="/en/docs/concepts/styling/designer"/>. If customizability is desired in your
97
108
design system, CSS properties or design tokens can be defined in the Designer for this purpose. So that the own theme
98
109
can be shared across projects, the theme is packaged in an NPM package and can be made available via any registry.
99
110
</p>
@@ -115,6 +126,12 @@ stateDiagram-v2
115
126
<p>
116
127
Own specific components, which are not provided by KoliBri and unfortunately do not fit to the KoliBri component
117
128
variety, can be built in own component libraries and maintained independently. For this purpose, we offer the
118
-
so-called <strong>KoliBri-Factory</strong> (Stack) (see <KolLink_label="Modularization"_href="https://github.com/public-ui/kolibri/blob/main/docs/ARCHITECTURE.md#erweitert"_target="_blank" />).
0 commit comments