The New CSSA Tailwind alternative for semantic, zero-config CSS
If you're tired of utility class overload or build-step complexity, The New CSS gives you a clean baseline with readable HTML.
When Tailwind is great
- +
Large apps with established utility workflows
- +
Teams committed to config-driven design tokens
When The New CSS is a better fit
- ✓
You want semantic HTML and readable markup
- ✓
You don't want a build step
- ✓
You want a lightweight baseline for fast sites
Comparison
| Tailwind | The New CSS | |
|---|---|---|
| Build step | Usually yes | No |
| HTML readability | Low (utility-heavy) | High (semantic-first) |
| Bundle size mindset | Depends on build | Small by default |
| Customization | Config-driven | CSS variables + real CSS |
| Learning curve | Medium | Low |
| Best for | Apps with utility workflows | Clean baselines + fast sites |
Migration notes
You can adopt The New CSS incrementally: start with typography + layout, then move components as needed.
<!-- Step 1: Add The New CSS -->
<link rel="stylesheet" href="https://unpkg.com/the-new-css/dist/the-new-css.min.css">
<!-- Step 2: Start using semantic markup -->
<article>
<h1>Your content</h1>
<p>Clean and readable.</p>
</article>