-
flynt
Component based WordPress starter theme, powered by ACF Pro and Timber, optimized for a11y and fast page load results. (by flyntwp)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The underlying problem I see that Tailwind solves is component-izing a single idea. It does that pretty well. You can point to a single stack of code and say "this one thing is a navbar" and it's easy to know where to make changes. No searching, no stress.
What I haven't seen Tailwind do well on my projects is respond to change in the same way other methods would. I'm not saying it isn't possible, just that the several projects I've seen, it was a big pain.
A method I've been quite fond of to accomplish the same task, but remove the difficulties this author's other posts articulate, is to recreate the concept of a component in a single folder. Much like you would a Vue single-file component. If you read the "Components" heading here you'll get a good feel for it by looking at the folder/file structure:
* https://github.com/flyntwp/flynt#components
That same idea I've enabled in a framework/language-agnostic way with an NPM module I created (not public). It watches the folder, namespaces everything like a single-file Vue component (using a manifest name or defaults to the folder name), and with a bit of config you can even do intelligent vendor/tree-shaking across all components and themes. You can even have components inherit theme sass/js files.
This solution is nice because devs get the "one source of editing" in a single folder, it's performant, and it's agnostic to language/frameworks. Point to a folder of components, specify a dist folder, and you're done unless you want to modify config. Parallel execution of all components being built, it's also fast!
I'm only saying all of this because I'm curious if there are Tailwind users out there that could teach me if Tailwind solves other problems I'm not seeing. Oor if this type of solution would be something I should open source. It ends up being a pretty simple Webpack file under the hood.
I still don't get Tailwind either but I found https://github.com/seek-oss/vanilla-extract recently which solves the TS/CSS modules nicely. All the styles are extracted at compile time so no overhead like most CSS-in-JS.