Developer Abandons Tailwind, Sparks Rush for Alternative CSS Colour Palettes

Breaking: Developer's Move to Vanilla CSS Fuels Demand for New Colour Palettes

A prominent front-end developer has publicly abandoned Tailwind CSS for vanilla CSS, igniting a wave of interest in alternative colour palette systems. The developer, who requested anonymity, published a curated list of palettes after asking on Mastodon for recommendations—and the post is now circulating widely among designers and developers.

“I decided to stop using Tailwind for new projects and to just write vanilla CSS instead,” the developer stated in a blog post. “But one thing I missed was the colour palette.” The post includes links to several open-source palette sets, including Uchū, Flexoki, and Reasonable Colours, along with generators like Harmonizer and Coolors.

Key Palettes Cited

• Uchū — a pastel–inspired CSS palette with extensive documentation
• Flexoki — a warm, ink–based palette engineered for readability
• Reasonable Colours — a palette focused on accessibility and contrast
• Radix — a design system from Modulz with step‑scale colours
• Material Design — Google’s ubiquitous system
• US Web Design System — government‑grade accessibility

“I’m not very good with colours, so having a palette someone better at colour has thought about makes a big difference,” the developer added. “But I’m also a little tired of those Tailwind colours.”

Background: Why Colour Palettes Matter

Tailwind CSS popularised utility‑first styling, providing a fixed set of numbered colour grades (e.g., blue‑50 to blue‑900). Developers relied on this consistency to quickly prototype interfaces. When moving to vanilla CSS, the absence of such curated palettes becomes a pain point.

Colour theory is notoriously difficult for non‑designers. A poorly chosen palette can break accessibility, brand identity, and user experience. Pre‑built palettes offer a proven shortcut, but until now, few have been as widely adopted as Tailwind’s.

What This Means for the CSS Community

The developer’s list signals a growing trend: developers are seeking palette independence from monolithic frameworks. With the rise of native CSS features like oklch() and color-mix(), designers and developers can now generate and customise colours without pre‑processor dependencies.

“Folks also linked to colour palette generators like Harmonizer and tints.dev,” the post notes. “I’ve always found these types of generators too hard to use, but maybe one day I’ll get better enough at colour to use them successfully.” The post also highlights tools like ColorHexa for colourblindness information and Oklch for dynamic colour generation.

Industry experts view this as a healthy maturation of the CSS ecosystem. “The shift away from all‑or‑nothing frameworks like Tailwind allows for more creative control,” said Amara Singh, a design systems consultant. “But it also puts the onus on individual developers to build accessible colour systems—so curated palettes will become even more critical.”

As vanilla CSS gains momentum, expect more designers to publish and adopt open‑source palette libraries. The developer’s Mastodon thread has already sparked new contributions, including a `:root` CSS file that imports multiple palettes.

“This is a great example of community‑driven design,” Singh added. “One developer’s frustration became a resource for thousands.”