Simplify and increase clarity
This commit is contained in:
@@ -1,24 +1,23 @@
|
|||||||
---
|
---
|
||||||
title: "Tailwind CSS"
|
title: "Tailwind CSS"
|
||||||
ring: trial quadrant: languages-and-frameworks
|
ring: trial
|
||||||
|
quadrant: languages-and-frameworks
|
||||||
|
|
||||||
---
|
---
|
||||||
Tailwind CSS is a utility first css framework which heavily utilizes css classes. What seems a very "different" approach
|
Tailwind CSS is a framework that heavily utilizes CSS classes.
|
||||||
in the beginning turns into a big "ah-ha-moment" during development and even more during build step. The classes
|
What seems to be a very different approach in the beginning, turns into a big "ah-ha-moment" during development and even more during the build step.
|
||||||
utilized are entirely generated based on a free to edit configuration file which outlines for example the entire design
|
CSS classes are entirely generated based on a configuration file that outlines the entire design system including states, nuances, etc.
|
||||||
system including states, nuances and so forth. Tailwinds high flexibility results in a very ux/design aligned set of css
|
Tailwind's high flexibility results in a set of CSS classes aligned with UX/design, requiring just a fraction of code compared to a self-built solution.
|
||||||
classes with a fraction of writing code compared to a self built solution. For example colors, sizes, spaces etc. can
|
Colours, sizes, spaces etc. can have meaningful names that are easy to remember and shared between developers and designers.
|
||||||
have meaningful names that are easy to remember and shared between devs and designers. This of course results in a
|
In turn, this results in a shared language with less explanation required.
|
||||||
shared language with lesser explanation required. To sum the positive experience up Tailwind CSS has furthermore a deep
|
Support for deep integration into the development and build processes ensure optimized build times with incremental rebuilds only on parts really necessary.
|
||||||
integration into the dev & build processes which means, during built time it's recognized which parts are really
|
This obviously leads to very small build sizes with nearly 100% CSS coverage.
|
||||||
necessary. This obviously lead to very small build sizes with a nearly 100% css coverage.
|
|
||||||
|
|
||||||
The deep integration and the extraordinary small build sizes were main aspects for us to choose Tailwind CSS for
|
The deep integration and the extraordinary small build sizes were the main aspects for us to choose Tailwind CSS for resource-limited projects in the field of industry 4.0.
|
||||||
resource limited industry 4.0 projects. These projects have a huge demand on a variety of interaction forms.
|
These projects have a huge demand on a variety of interaction forms.
|
||||||
|
|
||||||
Tailwind helps us fast-forward to fulfil modern user expectations by reducing complexity of sophisticated industry
|
Tailwind helps us to fulfil modern user expectations by reducing the complexity of sophisticated industrial processes with a multi-device approach.
|
||||||
processes in a multi device approach.
|
|
||||||
|
|
||||||
This is unexpressed expected by nowadays operators even in industry processes because the evolution from e.g. a classic
|
This is an unspoken expectation of today's operators of industrial processes. The evolution from classic
|
||||||
cellular phone towards a smartphone has proven, there is still a huge untapped potential for usability improvements and
|
cellular phones towards smartphones showed, there is still a huge untapped potential for usability improvements and
|
||||||
adaptivity driven processes, that reduce complexity especially the industry 4.0 field.
|
adaptive processes, that reduce complexity especially the industry 4.0 field.
|
||||||
|
|||||||
Reference in New Issue
Block a user