Design comparison
Solution retrospective
I had a tough time figuring out the best DRY approach, I would love to hear what the best DYR approach are there in relation to sass
Community feedback
- @DesignAssemblyPosted over 2 years ago
Hi There is no "best DRY Approach" really but there are meaningful guidelines on how to implement styling to not create bloat. I find breaking down the site into "components" that are reused across the site. then create a class for those components and if there is a small change that needs to be added to one of the components i would just use the @extend method to extend on the components class. But other than that break down your sass files into digestible files so it becomes easier for your to see what it it your working on. use good naming convention when it comes to class names ( I use the BEM Model - works for me) hope this helps point your in the right direction
Happy Coding
Marked as helpful0@justinepetersonPosted over 2 years ago@DesignAssembly Hi Gavin, Thank you for your response and recommendation, I have been working on naming convention and components, I am implementing the improvements in my next project,
0
Please log in to post a comment
Log in with GitHubJoin our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord