Comments on Writing CSS on Growing Teams

12 Reader Comments

Back to the Post
  1. I agree - once you’re nailed the communication everything falls into place. Coding in a team can be tough but that’s often down to the perceived efficiency of working alone.

    Copy & paste the code below to embed this comment.
  2. We started building a styleguide to have the common set of UI patterns. Design team drives defining these patterns and continually updating or adding to the styleguide. This not only helps maintain consistency across your product, but also reduces the amount of CSS written. We simply use selectors from the styleguide, we write CSS for very one-off cases and padding/margins. This has been extremely helpful and easy to bring engineers onboard. Styleguide can also guide people in to writing semantic HTML. Check out KSS (Knyle Stylesheets). It was simple to set up. You can specify how the markup should be for consuming the CSS.

    Copy & paste the code below to embed this comment.
  3. Have you found that implementing any sort of linter on your SASS has helped any? I’ve seen several projects that can look at nesting depth such as this one: https://github.com/brigade/scss-lint/blob/master/lib/scss_lint/linter/README.md#nestingdepth

    I find it to be a rather interesting concept, but have yet to implement it on anything I’ve worked on because I’m not generally working on teams with others.

    Copy & paste the code below to embed this comment.
  4. On our recent project we had 3 to 4 people working in the CSS at once, and it caused a lot of issues with shared CSS fixes in one place breaking things in another.
    Things that helped included using a global CSS file split out into sections, then local CSS files for templates, and some CSS files shared in specific areas.  Then one person became a gatekeeper on the global CSS file, and people would be assigned responsibilities for particular shared files.  Any changes needed would have to be approved by those people.  Also ensuring the same front end dev worked on the same template helped, plus as you say communication was key, particularly in terms of people knowing what other people were working on at any given time.
    Also ensuring people knew how to use Git properly was important to avoid them making mistakes resolving clashes.

    Copy & paste the code below to embed this comment.
  5. Thanks Susan Robertson -Nice article about layout,and framework and CSS styles.

    We had a great experience with Nety Design group when building out our website.

    Copy & paste the code below to embed this comment.
  6. Vital question regarding CSS that nobody has provided an answer to in many forums I’ve posted if I may please.  I currently use the weebly template provided by my web hoster Ipage for my site which when I try to combine CSS & JS files as the major setback in optimizing my uploading speed, as soon as I think I have saved the changes, the software reverts back to the weebly template. I have tried rebuilding the site from scratch in wordpress but as soon as I add a couple of vital features like a contact form by installing a plug-in, the site becomes larger in size than the original template. Is there another software that be a better choice? Thank you!

    Copy & paste the code below to embed this comment.
  7. We used that for Fondation Foch

    Copy & paste the code below to embed this comment.
  8. Nice. We use SMACSS as inspiration for CSS conventions as well. I think web components will also be a huge improvement to separate / isolate CSS. This is already happening in Ember https://github.com/ebryn/ember-component-css

    Copy & paste the code below to embed this comment.
  9. I have gained some new and valuable knowledge from it. Thank you for Sharing .

    Copy & paste the code below to embed this comment.
  10. GREAT post admin thanks.

    Copy & paste the code below to embed this comment.
  11. Copy & paste the code below to embed this comment.
  12. yah really nyc post
    Cashback + Moneyback

    Copy & paste the code below to embed this comment.