Currently, both mixins and rulesets sometimes live within the same Sass file. For example, elements/_typography includes rulesets for base HTML elements, but also includes Sass mixins. This prevents someone from being able to import just the mixins into their Sass project and would be much more usable if they were moved to a separate, mixins-only, file.
I'd propose either:
Create a core/_mixins.scss file, similar to how you currently have a core/_variables.scss file
Or, preferably, follow a pattern like ITCSS where there's a tools and settings layer for things like mixins and variables.
@sawyerh thanks for opening this issue. This sounds like a great idea to helping enhance the customization options for the Standards. Looking forward to reviewing your pull request!
Currently, both mixins and rulesets sometimes live within the same Sass file. For example,
elements/_typography
includes rulesets for base HTML elements, but also includes Sass mixins. This prevents someone from being able to import just the mixins into their Sass project and would be much more usable if they were moved to a separate, mixins-only, file.I'd propose either:
core/_mixins.scss
file, similar to how you currently have acore/_variables.scss
filetools
andsettings
layer for things like mixins and variables.This would allow an existing Sass project to do:
I'd be happy to make this pull request, but would like to get your thoughts before moving things around 😁
cc #1342