jamstack.org VS Tailwind CSS

Docusaurus is a Jamstack SSG (Static Site Generator) mainly intended for documentation and blog websites. It is a Meta Open Source project. Its configuration is done mainly through a JavaScript file called docusaurus.config.js.

Netlify has gained popularity among developers for its ease of use and powerful features. It's a great option for hosting static websites or Jamstack applications.

Jamstack Org

Jamstack architecture continues to gain popularity as a modern web development approach that focuses on pre-rendered content served from a CDN. Some benefits of Jamstack include better performance, lower cost, and greater scalability. Expect to see growth in Jamstack frameworks like Gatsby, Next.js and Nuxt.js in 2023.

More importantly, Netlify, the creator and stewards of the term Jamstack including it's canonical site, has largely abandoned the term as well, in favor of a "composable web" term that better aligns with their ambitions around becoming a broader enterprise platform including content (with tools like Netlify Connect).

I have been using the hosting environment provided by Netlify for years. I am aware there are several available including Vercelli and Heroku, to name a few, but Netlify was the first I tried and it continues to work well. It links into my Git repos on BitBucket and also offers Functions-as-a-Service (FaaS) for experimentation and small projects. Netlify is also a prime advocate of the JAMStack architecture that is gaining considerable interest.

You should check out JamStack. The premise is that the majority of your site is static content and you can push it out to CDNs that are frequently cheap or free.

Perhaps this is worth checking out and utilizing when I have the time to attempt another JAMstack project. Possibly Eleventy?

Lastly, Tailwind CSS is a utility-first CSS framework packed with classes like flex, pt-4, text-center, and rotate-90 that can be composed to build any design, directly in your markup.

Tailwind CSS

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.