# CSS Resets

CSS resets are stylesheets containing CSS rules that alter or remove browser user-agent defaults to provide a consistent starting point for web styling.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Moving away from Tailwind, and learning to structure my CSS

DevFeed: [Moving away from Tailwind, and learning to structure my CSS](<https://devfeed.tech/articles/moving-away-from-tailwind-and-learning-to-structure-my-css-21129.md>)

Original publisher: [Read original article](<https://jvns.ca/blog/2026/05/15/moving-away-from-tailwind--and-learning-to-structure-my-css-/>)

Author: Julia Evans

Published: 2026-05-15T00:00:00Z

Content type: article

Language: en

Sources: [Julia Evans](<https://devfeed.tech/sources/julia-evans.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [Tailwind CSS](<https://devfeed.tech/topics/tailwind.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [CSS Resets](<https://devfeed.tech/topics/css-reset.md>), [Code](<https://devfeed.tech/topics/code.md>), [Responsive Design](<https://devfeed.tech/topics/responsive-design.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [css](<https://devfeed.tech/tags/css.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [responsive-design](<https://devfeed.tech/tags/responsive-design.md>), [tailwind](<https://devfeed.tech/tags/tailwind.md>)

### AI overview

The author describes migrating several sites from Tailwind to semantic HTML and vanilla CSS, using lessons from Tailwind to create clearer systems for structuring CSS. The article discusses resets, components, colors, font sizes, utility classes, spacing, responsive design, and the build system.

### Source excerpt

Hello! 8 years ago, I wrote excitedly about discovering Tailwind. At that time I really had no idea how to structure my CSS code and given the choice between a pile of complete chaos and Tailwind, I was really happy to choose Tailwind. It helped me make a lot of tiny sites! I spent the last week or so migrating a couple of sites away from Tailwind and towards more semantic HTML + vanilla CSS, and it was SO fun and SO interesting, so here are some things I learned! As usual I'm not a full-time frontend developer and so all of my CSS learning has happened in fits and starts over many years. it turns out Tailwind taught me a lot When I started thinking about structuring CSS, I was intimidated at first: I'm not very good at structuring my CSS! But then I started reading blog posts talking about how to structure CSS (like A whole cascade of layers or How I write CSS in 2024) and I realized a couple of things: Every CSS code base has a bunch of different things going on (layouts! fonts! colours! common components!) It's extremely useful to have systems or guidelines to manage each of those things, otherwise things descend into chaos Tailwind has systems for some of these, and I already know those systems! Maybe I can imitate the systems I like! For example, Tailwind has: a reset stylesheet a colour palette a font scale the systems I'm going to talk about I'm going to talk about a few aspects of my CSS codebase and my thoughts so far what kind of rules I want to impose on the codebase for each one. Some of them are copied from Tailwind and some aren't. reset components colours font sizes utility classes the base spacing responsive design the build system 1. reset I just copied Tailwind's "preflight styles" by going into tailwind.css and copying the first 200 lines or so. I noticed that I've developed a relationship with Tailwind's CSS reset over time, for example Tailwind sets box-sizing: border-box on every element (which means that an element's width includes its padding