Atomizer

FYI, we are deprecating the acss.io domain. The website will continue to live on acss-io.github.io/atomizer/. Please update your links.

Update 5.2.0 @AtomicCSS has been updated to the latest version on webmaker.app/app (Extension updates in next few days)! Now use latest features like Grids and more! ✨

#StateOfCSS this years includes a wider range and updated list of tools. It's definitely not a full list, but still very happy to see that my suggestion to include postcss-preset-env, @lightningcss and @projectwallace got accepted.

FYI, atomizer@3.28.0 was released with support for the inset CSS property. Check out the reference page for details. #inset" target="_blank" rel="nofollow noopener">acss.io/reference.html… #atomiccss #css

Container Queries support was added in v3.26.0. Check it out when you get a chance and let us know of any questions or comments. #container-queries" target="_blank" rel="nofollow noopener">acss.io/breakpoints.ht…

@rogueyoshi_FGC For the reset, Tailwind is more opinionated in its default set of styles. We allow apps to use any reset they prefer. We feel this makes atomizer more flexible for apps.

@rogueyoshi_FGC For the description on hover, it could be useful, but atomizer classes are just abbreviations for the css properties. Most of the time classes are self explanatory. Tailwind needs it because there isn’t always a 1:1 relationship between TW and the CSS.

atomizer@3.23.0 has been published with support for 20 new #CSS properties. Please check out the release notes for details and example usage. github.com/acss-io/atomiz…

Every time I heard people praising Tailwind CSS I feel like @AtomicCSS is way under-appreciated :) Witnessing from the start (and took lots of bullets), I feel like it's important to credit back pioneering work (and it's still working perfectly fine after years)

Really enjoyed this interview with @7h1322yk0813n72 on the history of @AtomicCSS! Truly pioneering work that deserves an enormous amount of credit — Tailwind works virtually the same way at this point but we stumbled our way here *many* years later. css-tricks.com/thierry-koblen…

@Mokshit06 Great idea. Something we could add to atomizer as well.

Introducing a library to make tailwind DX so much better... typewind ✨ The magic of Tailwind combined with the safety of Typescript github.com/mokshit06/type…

@rogueyoshi_FGC What does this extension do differently from the original one?

@AtomicCSS can you link to the page for the official extension

@rogueyoshi_FGC That’s an interesting idea. Can you share a screenshot of how it works?

@AtomicCSS Would you guys make a plugin that shows class definitions on hover like the tailwind one does? That will extremely increase ease of use.

@rogueyoshi_FGC That’s not a version supported by us. Unless it’s just the intl version.

@AtomicCSS Also this version of the extension doesn't seem to be live.

@rogueyoshi_FGC Interesting and strange. There must be something with the inclusion of the style tag that triggers a new build.

@AtomicCSS Hi, HMR seems to be broken in your Sveltekit sample code. Changes won't reload live in dev mode, seems like a bug. Tried the Vite integration to, but no luck. acss.io/integrations/s…

@whoisryosuke Maybe complex class chaining should be moved to vanilla css or just add a new line after each class to make it easier to read.

This is the main thing that stops me from using atomic CSS libraries like Tailwind. They need a simpler, more human readable API (like style component props) to scale appropriately. There’s too much onus on the user here that could be deferred to systems and utilities.

@MatthewDeaners You can use both. But really it comes down to maintainability and deduplication of CSS as the project grows.

@mattaningram @b_e_n_t_e_n @Hicksyfern @hankchizljaw That’s been our message all these years. Use atomizer classes where it makes sense (simple css use cases) and vanilla css for more advanced css usage.

@b_e_n_t_e_n @Hicksyfern @hankchizljaw Oh totally, I use utility classes in my projects as well, just not ONLY utility classes the way I see many Tailwind advocates go. I just want there to be more realistic discussion for new devs coming in so they don't just hear that 100% Tailwind is the way to learn styling.

@blurfxo What issues are you having?

atomic css 라이브러리는 계속 봐도 적응이 안된다