7. What can we do better
better? us? wha’ ya sayin bruva
8. Always use icon fonts
• Wherever possible
• works on everything (even oldIE)
• Less need for SPRITES (they can do one)
• Future proof
(Caters for iPhone11 Plus Plus)
9. Inconsistencies
• Between code styles
• Get to know the same front end
• Use the same modules, mixins
• Normalise the designs
• Whitespace
15. Style Guides
• Consistency with buttons
• Consistency with colours
• Consistency with spacing
• Consistency with elements
• tables
• infographics
• buttons
• forms
16. Style Guides II
• When?
Design phrase, after first set of designs have been
approved
• Why?
Designers: When a new designer takes over, there’s a
clear point of reference for existing styles, no need to
trawl through loads of pages.
Devs: Helps us to keep our code modular, take the
aspects of the style guide and code them individually.
• Time / Money saving?
You bet!
23. General Improvements
• Avoid using grids unnecessarily
• * { box-sizing:border-box }
• Re-factor straight away
• Responsive mixins
• %’s over px’s
• Keep media queries within the elements
• Try not to overuse %silent-classes
• If you need to center vertically, consider absolute positioning
first (you can maybe utilise image-size() compass method)
• Keep your JS Modular on larger projects
• Keep experimenting!