A Fluid Grid Calculator
Build your own fluid grid systems.
Build your own fluid grid systems.
CSS code that is perfect for other developers.
High-level guidelines from writing manageable, maintainable CSS.
How to build big, scalable front-ends.
As sites get bigger, selectors should get shorter.
Why you should always try and apply margins in one direction only.
Harry Roberts' talk at Front-Trends 2012.
Explaining OOCSS and the use of classes.
Things to avoid in your code.
An introduction.
“If you’re starting a new job as a developer, place a copy of HTML for Dummies on your desk on the first day, see if anyone says anything…”
Discussing the fluid grid system behind inuit.css.
A nestable, Sass-based, responsive grid system.
A way to isolate hacky, quick-fix CSS.
“I secretly judge people who write ‘0px’ in their CSS…”
A better way to flag something as unique.
“Look after yourself, and with everything you do, make it count.”
“You know you’ve picked well when you can have a Skype conversation with your girlfriend about the intricacies of spacing em dashes…”
Approaches to maintain a better codebase.
How to do it with multiple remotes.
“The secret is, there is no secret. It’s all just a lot of continued, hard work.”
Approaches for writing manageable, scalable CSS.
A crude proof of concept.
Writing better quality CSS.
“Think of a preprocessor as a magnifying glass: it can make good CSS great, but bad CSS terrible. It’s not a magic bullet.”
Code is only a small part of a developer's job.
How to write self-documenting CSS.
An advanced principle to try and apply to CSS.
From BEM to BEMIT with some small additions.
When it’s OK to use !important.
How you can use the tool to get insightful metrics about your style sheets.
Ways to deal with legacy code.
Tutorial and demo.
A technique for images with a low change rate.
What it is and how to deal with it.
Why to always favor the longhand syntax.
Simple rules to drastically improve your text quality.
Things to avoid in your code.
When it comes to readable code, most of us could do better.
Let’s find out how well we handle failures.
Simple technique to identify dead code on a live site.
Demonstrate and observe slow-loading resources.
How and when browsers download images.
No more best-guessing browser support for your site.