Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

Sass, mobile first, Recipe Challenge

sass/scss, accessibility
P
Scott•310
@ldg
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm happy with my use of mixins in this challenge. I wanted a simple way to add all the text styles from the project's style guide as a single property. The mixins did just that, I was able to add all the text preset styles to a mixin an call them with an @include mixin-name to my stylesheets.

If I was to do it again, I think I'd try to add an arguement to the mixins, so I could specify whether the font-weight was regular or bold. I notice that there are instances where I have mixins that are duplicate, with the exception of the font-weignt. I think that would make the Sass a bit more efficient.

What challenges did you encounter, and how did you overcome them?

I haven't really worked with html tables all that much, so I had to do some reading on MDN to understand how to use them.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Scott's solution.

Join 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

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner
  • Use cases

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License