https://pusher.com/sessions/meetup/london-css/mistakes-were-made
- Breakout components/patterns that will provide most value first
- Documentation is necessary; "the code describes itself" is not good enough
- Explain & Educate! Make sure all business groups know what you are working toward (ie. consistent branding)
- You won't get time to work on it from the business; build little bit at a time while you are working on features; it's just part of your process, like tests
- Design team NEEDS to be involved
- Be selective on which components to include; gives you more time to determine patterns and designs to solidify
- Naming is hard, but do it right the first time; make it so that you know what it does and what it is so that you can find it easier later
- Don't solve problems you don't have yet
- The StyleGuide is ongoing and never done
- Technology stack: Stability over cutting edge so that you don't spend too much time wrestling with it and focus on the styleguide
- Funding Tree built the styleguide separately from their app(s)
- They also use BEM with a flavor of ITCSS and SMACSS
- BEM helps with the style "bleed through"
- Other companies that have done this have had bad experience with developers changing the markup and therefore breaking the style
- In general, it seems it's normal for developers to be anti-markup and anti-CSS