devprotocol.xyz VS Tailwind CSS

No doubt Dev Protocol, super small market cap, legit team.

Dev Protocol has a crazy low market cap and a solid team, which you can follow along with on their Discord

Without hesitation DEV. Has a great team with massive upside potential. Insanely undervalued atm.

I have decided to start with something simple. "good first issue". I have found such an issue - it was simply putting images where they belong. At first, however, I thought I had to remove backgrounds myself, which I definitely can and know how to do. I was happy to actually do something useful. However, it was a more brain dead task than I thought. I just had to wait till someone adds images to the issue and put those in a folder. Not really fun, nor skilled task. I have gotten very confused in that issue just because of communication. As you might see, there were many messages in that thread. They have also apparently messed up the images they sent, so they had to fix them again o_O. Idk, it was a weird experience for a first issue, which wasn't even a challenging one.

This was my first time building a complete project as a contribution. I proudly contributed to Web3Community/devprotocol.xyz.

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.