@AceKahuna
Posted
Hey there Ben, checked out your code and it looks fine. No need to worry about nesting since it helps out define the properties much efficiently and helps avoid making mistakes while calling a certain class or an element in vanilla CSS. On the media queries, you can create a @Mixin instead of having to write the code manually.
@mixin tab-land{
@media screen and (min-width: 992px) {
@content;
}
}
Set a min-width and max-width for the elements to avoid it squishing in the mobile view
@BenSeagrave
Posted
@kahunaako10 Thanks for your swift reply.
Could you please explain to me the benefits of writing the media queries with the mixin instead of css. Please tell me if I am wrong, but the only benefit I can see is that instead of writing the full media query in my SCSS, I can instead write it somewhere more hidden (another file or top/bottom etc) and then write a shorter syntax to include the same code.
Seeing as the difference is between:
@media only screen and (min-width: 992px) {
body {
background: red;
}
}
and :
@include desktop-break {
body: background: red;
}
I struggle to see the benefit for one single query. If however, I was to add an argument to the mixin so I could dynamically change the breakpoint dimensions, this would seem like it may be worth the extra code.
Thanks again for your reply and sorry for the long winded response. I just want to make sure I get your point so I can be sure to use it correctly in the future!
Again this may just be me being incorrect so please tell me if so.
@AceKahuna
Posted
Using the Mixin is helpful since instead of writing the media queries at the bottom you can easily write them within the element. For example,
body{
background-image: url('/images/bg-intro-mobile.png');
background-repeat: no-repeat;
background-color: $primarycolor;
overflow-x: hidden;
@include responsive(tab-port){
display: flex;
align-items: center;
flex-direction: column;
max-width: 100%;
background-size: cover;
}
}
for the case above you include the mixin within the element to avoid having to scroll each time to confirm the properties. You can create an SCSS file to contain the media queries breakpoints to efficiently work it. Check out my media queries file.
@AceKahuna
Posted
@kahunaako10 it's within the body element tried editing It but still, it won't display
@BenSeagrave
Posted
@kahunaako1 Great explanation, thanks!
I'll be sure to use your example in my future projects.
@AceKahuna
Posted
@BenSeagrave You're welcome Ben
