Jeremy Clarke's updates Load more

  • Jeremy Clarke
    • Jeremy Clarke Jeremy Clarke @Andy Novocin 1) Yes that's a good solution. Use a class like .menu-hidden then add it to a group like #HIDDEN-BY-DEFAULT and use jQuery to toggle that class on a given element. 2) I believe SASS is compatible with DRY CSS if you want it to be. Certainly my particular pattern for DRY could be converted into a background SASS library from which you basically duplicate groups for your particular projects with your particular selectors in them (something like Compass could be considered a DRY CSS library in many ways). Making your SASS create a DRY CSS outcome is mostly about how you use it, the important thing being that you avoid making the huge wet mess that so often results from sloppy use of preprocessors. About seeing groups in dev tools the important thing is to use the "extend" method in SASS rather than the "mixins". Mixins duplicate the properties from one selector to another, while extend duplicates selectors instead. So if you have .red-text and extend it for .header .edit you'll get: .red-text, .header .edit { RED } Rather than two separate declarations. Notably LESS ha(d/s) no equivalent to SASS's "extend" and is thus dead to me :P Also of note: The "extend" system in SASS doesn't work in media queries! Media queries are the one place where I can't get DRY CSS to work and have been forced to duplicate groups that need to be changed for each breakpoint. So extend being broken there has removed the one major reason I was planning to start using SASS as part of my DRY workflow.  2 weeks ago
  • Loading more posts…

Latest from people followed

  • Loading Loading..