Julia Evans shares her experience migrating personal sites from Tailwind CSS to vanilla CSS with semantic HTML. She outlines the CSS organization system she developed, covering nine areas: CSS reset (copied from Tailwind's preflight), component-based structure with scoped files, color palette via CSS variables, font size scale mirroring Tailwind's naming, utility classes, minimal base styles, spacing strategies using lobotomized owl selectors, responsive design with CSS Grid and auto-fit instead of media queries, and esbuild for production bundling. She explains why she left Tailwind — build system dependency, 2.8MB unoptimized CSS files, improved CSS skills, and desire for more flexibility — while acknowledging Tailwind taught her valuable structuring concepts she now replicates in vanilla CSS.

9m read timeFrom jvns.ca
Post cover image
Table of contents
it turns out Tailwind taught me a lotthe systems I’m going to talk about1. reset2. components3. colours4. font sizes5. utilities6. the base7. spacing8. responsive design: use more grid!9. the build system: esbuildwhy migrate away from Tailwind?CSS features I’m curious aboutthat’s all for now!
2 Comments

Sort: