CSS-Guidelines

High-level guidelines for writing manageable, maintainable CSS

Explore on GitHub Read Hacker News discussions

3Distinct people

4Mentions

0Explicit recommenders

3.6KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

High-level guidelines for writing manageable, maintainable CSS

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month4 dated mentions

Observed mentions: 2012-03-12 14:28:04 UTC to 2013-03-19 14:52:03 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Mar 2012	2012-03-01 00:00:00 UTC	2012-04-01 00:00:00 UTC	2	1	1
Apr 2012	2012-04-01 00:00:00 UTC	2012-05-01 00:00:00 UTC	0	0	0
May 2012	2012-05-01 00:00:00 UTC	2012-06-01 00:00:00 UTC	0	0	0
Jun 2012	2012-06-01 00:00:00 UTC	2012-07-01 00:00:00 UTC	0	0	0
Jul 2012	2012-07-01 00:00:00 UTC	2012-08-01 00:00:00 UTC	0	0	0
Aug 2012	2012-08-01 00:00:00 UTC	2012-09-01 00:00:00 UTC	0	0	0
Sep 2012	2012-09-01 00:00:00 UTC	2012-10-01 00:00:00 UTC	0	0	0
Oct 2012	2012-10-01 00:00:00 UTC	2012-11-01 00:00:00 UTC	1	1	0
Nov 2012	2012-11-01 00:00:00 UTC	2012-12-01 00:00:00 UTC	0	0	0
Dec 2012	2012-12-01 00:00:00 UTC	2013-01-01 00:00:00 UTC	0	0	0
Jan 2013	2013-01-01 00:00:00 UTC	2013-02-01 00:00:00 UTC	0	0	0
Feb 2013	2013-02-01 00:00:00 UTC	2013-03-01 00:00:00 UTC	0	0	0
Mar 2013	2013-03-01 00:00:00 UTC	2013-04-01 00:00:00 UTC	1	0	1

What Hacker News says

4 sources

no_more_death·Mar 19, 2013

Step 1: Learn to use the CSS profiler in Chrome. Also, here are some articles I found in my links list: CSS Stress Tester Bookmarklet (Copy into a bookmarklet. Then it will tell you the rules that are causing the most lag.) javascript:(function(d){var s=d.createElement('script');s.src='http://andy.edinborough.org/Demos/css-stress/stressTest.js?_... es=d.getElementsByTagName('script')[0];es.parentNode.insertBefore(s,es);var doit=function(){if(window.stressTest){stressTest.bookmarklet();}else{setTimeout(doit,100);}};doit();})(document); Old but still relevant I think: http://www.stevesouders.com/blog/2009/06/18/simplifying-css-... Text makes CSS slow (don't render too much): https://news.ycombinator.com/item?id=2232212 In general, following good guidelines might help: https://github.com/csswizardry/CSS-Guidelines

In The DOM isn't slow

Brajeshwar·Oct 18, 2012Submission

High-level guidelines for writing manageable and maintainable CSS

3 points · Open discussion

csswizardry·Mar 12, 2012

Catch all response: This document is a personal one, and for use at my place of work. I decided to share it in the hope that it might be useful to others but if you disagree with anything please remember; this is a document for me and Sky. You do not have to follow the advice given, nor do I provide any guarantee. — https://github.com/csswizardry/CSS-Guidelines/blob/master/RE... > Nope. Fair enough. > Nope. Fair enough. > If you're Facebook, and you have a deep and wide site architecture… We’re not Facebook, but we are big. > Nope. Again, grid systems are something that should be used on a case-by-case basis, according to the nature of the site you're building. Okay, as mentioned this is doc used largely at my place of work where we do use a grid system. For places that don’t use one then this basically means ‘don’t apply dimensions to co

Read the rest

mponents; leave structure to parents and wrappers’. Hard coding dimensions on components should be avoided at all costs. > Nope. What you're arguing against is a rule that has a high degree of specificity. I’m not. Heavily location selectors hinder flexibility; components should not rely too heavily on where they live, they should be movable as easily as possible. Shorter, less location-dependent selectors aid this. > Don't outright ban IDs just because you're not careful enough to write clean CSS. I believe I’ve got my CSS nailed, thanks. IDs will only ever hinder a CSS developer; they offer zero benefit (where CSS is concerned) over a class, thus why would you ever bother using them? If all they can do is harm then just cut them out; even the most careful developers can get tripped up by the overly specific nature of IDs. > Hahahahahahahahahhaa. I’ve just finished the rebuild a massive front-end, the project as a whole took over a year. Number of IE stylesheets: 0. It can be done.

In Show HN: I decided to document and share my high-level CSS best practices

csswizardry·Mar 12, 2012Submission

Show HN: I decided to document and share my high-level CSS best practices

223 points · Open discussion