Added more Tailwind showndown notes.

gnat · web-flow · commit da6bef3d20d4 · 2024-09-06T02:54:57.000-07:00
diff --git a/README.md b/README.md
@@ -52,6 +52,7 @@ Use whatever you'd like, but there's a few advantages with this approach over Ta
 * No high risk of eventually requiring a build step.
 * No chance of [deprecations](https://windicss.org/posts/sunsetting.html). 16 lines is infinitely maintainable.
 * Get the ultra-fast "inspect, play with styles, paste" workflow back.
+* No suffering from a lack of syntax highlighting on properties and units.
 * No suffering from FOUC (a flash of unstyled content).
 * Zero friction movement of styles between inline and `.css` files. Just replace `me`
 * No special tooling or plugins to install. Universal vanilla CSS. 
@@ -103,7 +104,12 @@ Tailwind verbosity goes up with more child elements.
     <div class="bg-[green]">green</div>
 </div>
 ```
-### CSS variables and child styling
+
+### CSS variables and child elements
+At first glance, **Tailwind Example 2** looks very promising! Exciting ...but:
+* 🔴 **Every child style requires a selector** so the short style advantage unfortunately disappears.
+  * This trivial example is the best case scenario for Tailwind.
+* 🔴 Not visible on github, but **zero highlighting for properties and units** begins to become painful.
 ```html
 <!doctype html>
 <html>
