WDCNZ - Writing Better CSS

29
Writing better CSS. @toni_b

description

Writing Better CSS, talk from @toni_b at WDCNZ July 2014.

Transcript of WDCNZ - Writing Better CSS

Page 1: WDCNZ - Writing Better CSS

Writing better CSS.

@toni_b

Page 2: WDCNZ - Writing Better CSS

I’m Toni.

Page 3: WDCNZ - Writing Better CSS
Page 4: WDCNZ - Writing Better CSS

WRITING CSSIS EASY.

Page 5: WDCNZ - Writing Better CSS

WRITING REALLY GOODCSS IS NOT.

Page 6: WDCNZ - Writing Better CSS

WHAT’S GOOD?

Page 7: WDCNZ - Writing Better CSS

I don’t think it means:

Cutting edge Performance

optimized

Page 8: WDCNZ - Writing Better CSS

Maintainable

Understandable

Well-planned

Page 9: WDCNZ - Writing Better CSS

Tip #1: Plan

Page 10: WDCNZ - Writing Better CSS

Browser Requirements

Page 11: WDCNZ - Writing Better CSS
Page 12: WDCNZ - Writing Better CSS

Coding Standards

Page 13: WDCNZ - Writing Better CSS
Page 14: WDCNZ - Writing Better CSS

Get your tools sorted

Concatenation & minification

Frameworks?

Page 15: WDCNZ - Writing Better CSS

Tip #2: Comment Table of contents

Logical grouping for easy maintenance

Weird stuff: Why the @*!^ you did that

thing.

Page 16: WDCNZ - Writing Better CSS

Tip #3: Create Structure

Page 17: WDCNZ - Writing Better CSS

The main.css dumping ground.

Divide CSS into logical files/sections

Page 18: WDCNZ - Writing Better CSS

“Build a system of components that you can re-use”

- Jonathan Snook

Page 19: WDCNZ - Writing Better CSS
Page 20: WDCNZ - Writing Better CSS

Tip #4: Build a pattern

library

Page 21: WDCNZ - Writing Better CSS

http://pea.rs

Page 22: WDCNZ - Writing Better CSS

Reusable components

Documentation

Page 23: WDCNZ - Writing Better CSS
Page 24: WDCNZ - Writing Better CSS
Page 25: WDCNZ - Writing Better CSS

Test Suite

Page 26: WDCNZ - Writing Better CSS
Page 27: WDCNZ - Writing Better CSS
Page 28: WDCNZ - Writing Better CSS

Maintainable.

Understandable.

Well-planned.

Page 29: WDCNZ - Writing Better CSS

thanks!@toni_b

tonibarrett.com