/explore
|
You are here 
|
vsupalov.com | ||
| | | | |
mzrn.sh
|
|
| | | | | Most websites I build start off as a blank Jekyll site with Tailwind CSS on top. | |
| | | | |
geoff.tuxpup.com
|
|
| | | | | I took a detour to try out the Smelte/Tailwind CSS UI gadgetry. I found lots to like about it, but it's not the right thing for me right now. Read on if you're interested in the detour. If you're trying to follow how I got to my end state, go here instead to see how I set things up for vanilla Tailwind. Adding Smelte and Tailwind CSS I'm not a web designer, and I have no ambitions of becoming one. | |
| | | | |
www.mattlayman.com
|
|
| | | | | How can you set up Tailwind CSS for your Django app on Heroku? In this article, we'll see how I did exactly that recently. I have a side project that uses Tailwind CSS. To get started quickly, I used the version from a Content Delivery Network (CDN) as Tailwind describes in the documentation. This worked fine initially while I got my project started, but the CDN version is huge (around 3MB). | |
| | | | |
www.voorhoede.nl
|
|
| | | Static websites don't update by themselves. We can now run a cron job in the new GitHub actions to trigger a Netlify deploy hook. | ||
