rmrk-web VS Tailwind CSS

Have you heard of RMRK? Some really cool stuff related to NFTs 2.0 are being developed for EVM (including 4 (for now) EIPs published).. Some of the EVM contributions are showcased in the https://evm.rmrk.app

If you are just starting out, I’d suggest to look at https://rmrk.app We have some of really cool NFT 2.0 features that might set your project apart from the currently existing ones ;)

at the top of rmrk.app there is a "GET KSM" button with some fiat on ramps

As for NFTs, here's the Kusama is RMRK - I don't know what the DOT equivalent is. I think that project will become a substrate module, and so will enable NFTs for all blockchains that use the module.

RMRK | Remote| EU only | Full Time | Fullstack React Typescript developer | https://rmrk.app

We are looking for a Full-Stack Typescript developer, with strong front-end skills. Namely React/Typescript/Next.js

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.