We discussed this at the last meeting. Here's some simple starter links. If you want to try SCSS out right now, simply set the Codepen CSS Preprocessor to SCSS (found in CSS settings) and fire away. (If you're using another IDE, you'll have to look that up.) I recommend SCSS to start because you can put normal CSS code in a .scss file and it will work normally. So it's a good way to introduce some new things slowly. (SCSS stands for "Sassy CSS" btw!)
The above examples use functions in their use of breakpoints. But here I take an approach that is uglier up front but will be less code when implemented. e.g. @include sm is shorter and clearer than @include bp(sm).
We discussed this at the last meeting. Here's some simple starter links. If you want to try SCSS out right now, simply set the Codepen CSS Preprocessor to SCSS (found in CSS settings) and fire away. (If you're using another IDE, you'll have to look that up.) I recommend SCSS to start because you can put normal CSS code in a .scss file and it will work normally. So it's a good way to introduce some new things slowly. (SCSS stands for "Sassy CSS" btw!)
Learn SASS in 15 Minutes
Write Better Media Queries With SASS
Using media queries in Sass 3.2
Creating a Dead Simple Sass Mixin to Handle Responsive Breakpoints
The above examples use functions in their use of breakpoints. But here I take an approach that is uglier up front but will be less code when implemented. e.g.
@include sm
is shorter and clearer than@include bp(sm)
.