play.tailwindcss.com VS twind

Another tip is to use https://play.tailwindcss.com/

I have not dealt with something like this before. However, you do not need to use a custom CSS equivalent. You can try out your utility classes here https://play.tailwindcss.com/ and see if you're getting the same results. If you're trying to give the div content more emphasis using the drop-shadow utility class, try drop-shadow-xl to make it stand out a bit more. Around the focus property, you mentioned perhaps using one of the conditional modifiers such as focus:drop-shadow-md may help. I have some lessons around tailwind you may want to watch https://youtu.be/R0E2qSXcmAY Good luck.

Are you looking for a CDN (to let you use Tailwind in an arbitrary environment where you can't install it) or simply a playground? For a playground the easiest is the official one https://play.tailwindcss.com/

Let's go to the Tailwind Play website and try it there. Remove all the code in the editor section so that we get a blank screen.

I'm a beginner and I don't know why tailwind behaves differently when used with svelte. I type this code on tailwind playground.

Here you don't need to sign up. https://tailwindcss.com/ Try the cdn or better yet https://play.tailwindcss.com/ if you want to try it out.

If you want to try Tailwind CSS, Tailwind Play and Play CDN are the quickest way you can get your hands dirty

Were going to use the Tailwind CSS Play tool. This will get us up and going fast and make sure youre environment is identical to mine.

I've been using Tailwind for a few months and I've been speeding up my development time so much by taking advantage of how easily I can take a Figma design from a competent designer and convert it over to html/CSS with https://play.tailwindcss.com.

If you're not familiar with Tailwind css, read the docs and follow step by step. If you were sent components, it's probably not the full site structure so that's why they don't look good. You could create a new Tailwind project and copy each code snippet/section and they will display correctly. You can also use: https://play.tailwindcss.com/ as your sandbox to test those components individually.

I think TW syntax is great as a CSS shorthand. I think it can be a great tool for making highly descriptive styles in a far more succinct fashion. I think if you you use Twind compiler and you store TW syntax outside of your templates/JSX and you just compile it down to descriptive class names, that's a great use of Tailwind. Then you get the advantage of meaningful names applied to elements in the template, and if you need to refactor/fix a style, then you can find it much easier. It also makes it a lot more dynamic, which standard Tailwind which can be a PITA to make dynamic (e.g. for dynamic behavior in Twind, you can have functions that generate TW style strings and use interpolated strings without having to worry about if the build-time TW compiler understands all the possibilities).

But at least you like something. And I get why people like Tailwind, but I end up finding it constricting for behavior that results in dynamic styles. But I've tried Twind which is a runtime TW compiler and it fixes most of my complaints and it has the same SSR-ability like Stitches & Emotion.

The CSS-in-JS library solves problems of global nature of CSS and of specificity by providing scoping in a unique class-name. It has some cost attached to it i.e run-time which is being solved by order libs vanilla-extract-css. I'm a big fan of tailwind and I honestly believe it is enough for your project. If you also need dynamic styles then CSS-in-JS is better over tailwind, though there are solutions like twind which provide a flavor of tailwind with the CSS-in-JS approach they do have all cons of any CSS-in- JS libraries. I'm very excited about styles by Facebook and waiting for the day it will be open-sourced or CSS itself evolves to me provide scoping and be more modular, until that day comes I'm betting on CSS-in-JS with stitches and vanilla-extract-css.

what framwork are you coming from? i honestly wouldn’t try fresh unless you are using tailwind - bootstrap components are jsx based, and fresh is based off islands architecture which would make integrating the two trickier since youd have to route through deno + the preact compat lib. if you really want to do it, read into this. that being said, tailwind is a very powerful tool. i use it daily in nearly every element on front end, and as someone who likes avoiding design as much as possible ive found tailwind (and twind) are extremely pleasant to work with since it’s mostly class/keyword based styling as opposed to css / sass / scss styling

I want to do something similar with Remix to make a separate stylesheet per route with content coming from a CMS like WordPress. I’ve had my eye on Twind once they add compatibility with v3 and all the JIT stuff. https://twind.dev/

When initializing a new project, Fresh will also ask if you want to use Twind, which is a Tailwind-to-JS library. If you choose this option, then you will have the power of Tailwind without creating a config file or using PostCSS, which I thought is pretty cool.

Try https://twind.dev/