/explore
|
You are here 
|
blog.ideotec.es | ||
| | | | |
www.billtalkstoomuch.com
|
|
| | | | | Ah. The pitfalls of AI. Turns out everywhere I turned I was getting instructions for installing Tailwind v3 and not v4. But Tailwind itself was installing v4. And in some cases, AI was comingling the instructions. That accounts for nonsense that follows. If you want an updated and, likely, correct | |
| | | | |
windicss.org
|
|
| | | | | Next generation utility-first CSS framework. | |
| | | | |
geoff.tuxpup.com
|
|
| | | | | Part of the appeal of Smelte was Tailwind CSS integration. After going back and trying Smelte some more, I concluded that it'd be easier to use Tailwind directly, at the cost of giving up some very convenient widtgetry. The Smelte widgets aren't comprehensive enough to use them all alone, and their customization of Tailwind makes it too hard to integrate things that rely on the vanilla utility classes. So here's how I'm integrating. | |
| | | | |
davedavies.dev
|
|
| | | Use 11ty Static Site Generator to fetch posts and pages from a WordPress blog, and build them into an entirely static website we can deploy to Netlify | ||
