Atomizer

A utility-first CSS library to create small, reusable CSS that scales as your website grows.

[Atomizer @AtomicCSS]

FYI, we are deprecating the https://t.co/AWV6yidljP domain. The website will continue to live on https://t.co/rK9c27kKn6. Please update your links.

[Web Maker @webmakerApp]

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

[romainmenke @romainmenke]

#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.

[Atomizer @AtomicCSS]

FYI, [email protected] was released with support for the inset CSS property. Check out the reference page for details.

https://t.co/6nxHZbSHI0

#atomiccss #css

[Atomizer @AtomicCSS]

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. https://t.co/Jr8UtHwPmj

[Atomizer @AtomicCSS]

@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.

[Atomizer @AtomicCSS]

[email protected] has been published with support for 20 new #CSS properties. Please check out the release notes for details and example usage. https://t.co/Mg0xQeQ6Rd

[Atomizer @AtomicCSS]

@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.

[Roderick Hsiao @roderickhsiao]

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)

[Adam Wathan @adamwathan]

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.

https://t.co/hjzBxZ5LuT

[Atomizer @AtomicCSS]

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

[Atomizer @AtomicCSS]

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

[Atomizer @AtomicCSS]

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

[Atomizer @AtomicCSS]

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

[Atomizer @AtomicCSS]

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

[Atomizer @AtomicCSS]

@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.

[Atomizer @AtomicCSS]

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

[Atomizer @AtomicCSS]

@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.

[Atomizer @AtomicCSS]

@blurfxo What issues are you having?