sage VS twin.macro

Hey there!

Using Django or Flask might be overkill for what you're trying to do. I suggest you to stick with WordPress, but check out the Sage/root style over at https://roots.io/sage.

It's not the classic WordPress; it's a modern, more secure version.

Also only use plugins when you absolutely have to, and if you do, stick with the pros (i.e. Gravityforms).

I've used WP alot (more than 1000s of websites) and I'm also using Python with Flask and FastAPI (but never used Django).

We develop custom themes with sage and acf blocks 10/10, you should try it.. https://roots.io/sage/

If you do ultimately end up having to build in WordPress I'd recommend checking out sage. https://roots.io/sage/

Well, WordPress keeps moving towards drag n drop / visual editing and that makes everything more complicated for people who just want a system to manage data. There are people out there who have invested a ton of time to try and bridge the gap between the direction of wordpress and modern templating features like Sage by Roots (https://roots.io/sage/)

A minimal theme combining Roots Sage 10 and Bootstrap 5.2 (at the time of writing this article 5.3 was an alpha release). and making use of the plugins in places.

Sage starter theme by Roots - this gives us the Blade template engine that we are familiar with from Laravel.

Twin Macro Github Repo. This is a great resource to help you pick up Twin’s syntax, learn more about the package, and keep up to date with the latest releases.

Personally I like twin.macro the most. It’s similar to the above but based on Tailwind.

twin.macro is a library that allows you to use these styles in your JavaScript code. This library works exactly like styled-components.

One of the more promising alternatives is twin.macro - a Babel macro that processes Tailwind classes to generate JS objects understandable by various CSS-in-JS libraries. The developer experience (DX) of using it is amazing as you not only get all of Tailwind’s features without much change to your code, but you also get much more flexibility - all that on top of the traditional benefits of CSS-in-JS. Here’s an example code:

twin.macro

If you use Tailwind with React a lot, and are wanting support for Styled Components, give Twin Macro a look. They're close to finishing support for TW v3 in their Releases section :)

The blocker for us using it is our use of an excellent library called twin.macro which is built against babel's transpilation APIs to parse tailwindcss directives at compile time so that they may be used with css-in-js libraries. This efficiently bundles your css so that you only ship the precise css you use. The problem is, it's all quite slow.