More Transparent UI Code

Start: April 17, 2015

With the nature of maintaining a large project, we often find that we spend more time reading markup and its styling through developer tools than we might do reading source CSS files.

This means that meaningful class names become invaluable for communicating rich information to other developers.

We need to say exactly what a class does, why it exists, where (else) it might already occur, whether or not we can reuse it elsewhere, and how safe it is to bind onto or modify.

This means that the names of the classes become documentation, and we can read all of that documentation right there in the view.

Wouldn’t it be nice to know the exact scope and reach of a selector from its name alone?

Register

TAGS:
CATEGORY: Events, Webinars
 
 

Popular posts

Related posts