File tree Expand file tree Collapse file tree 1 file changed +9
-1
lines changed Expand file tree Collapse file tree 1 file changed +9
-1
lines changed Original file line number Diff line number Diff line change @@ -52,6 +52,7 @@ Use whatever you'd like, but there's a few advantages with this approach over Ta
52
52
* No high risk of eventually requiring a build step.
53
53
* No chance of [ deprecations] ( https://windicss.org/posts/sunsetting.html ) . 16 lines is infinitely maintainable.
54
54
* Get the ultra-fast "inspect, play with styles, paste" workflow back.
55
+ * No suffering from missing syntax highlighting on properties and units.
55
56
* No suffering from FOUC (a flash of unstyled content).
56
57
* Zero friction movement of styles between inline and ` .css ` files. Just replace ` me `
57
58
* No special tooling or plugins to install. Universal vanilla CSS.
@@ -103,7 +104,14 @@ Tailwind verbosity goes up with more child elements.
103
104
<div class =" bg-[green]" >green</div >
104
105
</div >
105
106
```
106
- ### CSS variables and child styling
107
+
108
+ ### CSS variables and child elements
109
+ At first glance, ** Tailwind Example 2** looks very promising! Exciting ...but:
110
+ * 🔴 ** Every child style requires an explicit selector.**
111
+ * Tailwinds' shorthand advantages sadly disappear.
112
+ * Any more child styles added in Tailwind will become longer than vanilla CSS.
113
+ * This limited example is the best case scenario for Tailwind.
114
+ * 🔴 Not visible on github: ** no highlighting for properties and units** begins to be painful.
107
115
``` html
108
116
<!doctype html>
109
117
<html >
You can’t perform that action at this time.
0 commit comments