Skip to content

Commit

Permalink
Add notice to Tailwind CSS blog post about bundled configuration (#849)
Browse files Browse the repository at this point in the history
* Add notice to Tailwind CSS blog post about bundled configuration

Closes: #785

* Adjust wording
  • Loading branch information
jclusso authored Feb 26, 2024
1 parent f2f2594 commit 854eca8
Showing 1 changed file with 6 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,17 @@ author: jared
category: news
---

{%@ Note type: :warning do %}
#### This post is a bit outdated!
Since writing this post, automations were added to Bridgetown. To start using Tailwind CSS with Bridgetown, check out the [community-maintained automation](https://github.com/bridgetownrb/tailwindcss-automation).
{% end %}

Personally, [I'm a Bulma man myself](https://bulma.io), but I understand there are a ton of you out there who love [Tailwind CSS](https://tailwindcss.com) and won't give it up until they pry it out of your cold, dead hands.

So I'm pleased as Ruby-colored punch to [highlight this breezy tutorial by Andrew Mason][andrewm-blog] all about how you can quickly and easily set up a new Bridgetown website with Tailwind CSS and PostCSS.

From the [article][andrewm-blog]:

> If you have had Ruby/Rails/Jekyll experience, you should feel right at home with Bridgetown. Bridgetown also removes the barrier to entry for integrating webpack and all the goodies the JavaScript community has to offer.
[andrewm-blog]: https://andrewm.codes/blog/build-and-deploy-a-static-site-with-ruby-bridgetown-tailwindcss-and-netlify/
Expand Down

0 comments on commit 854eca8

Please sign in to comment.