↵

MaintainableCSS - an approach to writing modular, scalable and of course, maintainable CSS(maintainablecss.com)

over 7 years ago from Adam Silver, Interaction designer focused on inclusive design and design systems

  • Renato de LeãoRenato de Leão, over 7 years ago (edited over 7 years ago )

    You got me with the title, but Immediately stopped reading when I saw the line don't reuse. I'm not here to tell you what approach you should follow: if it works for you and your team, just great and keep it up.

    Specificity may save from HTML bloat, but gives you CSS bloat and on massive apps or fast-growing/iterative ones, it will be a nightmare to update every single component just because your client want to experiment something new.

    At the time of writing I tend to do a mashup of OOCSS, some utility (responsive) Atomic Classes and flavor everything with BEM Syntax.

    Either way i'll leave here some articles, that sum up my approach better than I can possibly explain on a DN comment:

    Actually read the hole blog of Harry Roberts csswizardry. Nope i don't have a referral program with him, he's just really good at what he does.

    11 points
    • Hamish TaplinHamish Taplin, over 7 years ago

      The Salesforce design system doesn't get mentioned enough. It's an amazing example of the principles of a modular design system actually working incredibly well in the wild.

      4 points