Re: [css-d] Theoretical Media Query question

On Tue, May 31, 2016 at 3:59 PM, Shawn Lawler wrote: > Add a little more efficiency into that second option and you've got the > method I use: > > In a sass partial that you'll import into your main scss file - build your > mixin(s): > $min-bp-large: 747px; > > @mixin bp-large

Re: [css-d] Theoretical Media Query question

Add a little more efficiency into that second option and you've got the method I use: In a sass partial that you'll import into your main scss file - build your mixin(s): $min-bp-large: 747px; @mixin bp-large { @media only screen and (min-width: $min-bp-large) { @content; } }

Re: [css-d] Theoretical Media Query question

On Tue, May 31, 2016 at 12:40 PM, Chris Rockwell wrote: > Sorry Tom, I completely glossed over your actual question. > > I can only guess that your method (fewer files I presume) is faster to > compile but I can't imagine that being anything noticeable. From an >

Re: [css-d] Theoretical Media Query question

Sorry Tom, I completely glossed over your actual question. I can only guess that your method (fewer files I presume) is faster to compile but I can't imagine that being anything noticeable. From an organization standpoint I strongly prefer breaking everything into components and including the

Re: [css-d] Theoretical Media Query question

I have used the method from the second article since I started using Sass. I break components/objects/atoms/whatever into their own file and it makes more sense, to me, to include the media query with the components. I make mine "more inline" though: .selector { color: red; @media

[css-d] Theoretical Media Query question

Listers, I was just reading a great article by Veerle Pieters ( here ) which linked to another article ( here ) that made me stop and think about how