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

Recipe Page using Sass/SCSS and build with Vite

sass/scss, vite
P
Michael•180
@Networksentinel
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 really proud of pushing through the difficulty of getting the mobile-to-tablet design transition smooth. It took a lot of trial and error, but I made it happen!

Also, even though my mixins weren’t super complicated, they definitely made my life easier and made the code more readable. Here’s one of them:

@mixin text-preset-1(
$font-family:'young-serif-regular', 
$font-weight:$font-weight-regular, 
$font-size:$font-size-xl, 
$line-height:$line-height-default, 
$letter-spacing:$letter-spacing-default) 
{
    font-family: $font-family;
    font-weight: $font-weight;
    font-size: $font-size;
    line-height: $line-height;
    letter-spacing: $letter-spacing;
}

Next time, I’d probably spend a bit more time studying the design and really thinking through the details, especially when it comes to layout for different screen sizes. I think that would save me a lot of time since I had to restructure my HTML a couple of times.

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

The biggest challenge I ran into was getting the mobile-to-tablet design transition just right:

  • On mobile, the image as wide as the screen and only the content has padding.
  • But on tablet, the image and content have the same width and the padding is mutual.

To get this right, I had to take a step back, look at my HTML structure, and rethink how to approach it - I ended up restructuring it a couple of times until everything lined up properly.

What specific areas of your project would you like help with?

I’d love some feedback on my code structure, especially when it comes to:

  • The way I’ve organized my mixins and variables
  • Any potential improvements to the modularity of my code
  • Suggestions for improving my HTML structure, particularly around semantic elements and accessibility

Any tips or suggestions would be super helpful!

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 Michael'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
Frontend Mentor logo

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

Frontend Mentor

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.