Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Responsive Recipe page

Sandip Tamang•60
@SandipTamangDev
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 most proud of how I reverse-engineered the design using just a single given font size (16px for paragraph text). From there, I calculated all other font sizes, card widths, and layout spacing by analyzing the 1440px and 375px views. I got it as close as possible to the original design, and that process really sharpened my eye for responsive scaling and proportions."

"If I were to do it again, I’d approach it with more confidence from the start and document my steps better—so I could both explain my logic clearly and speed up the process.

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

One of the main challenges I faced was with the title font not displaying correctly. I double-checked the font import and usage, but it still didn’t work—likely due to a browser or loading issue. I attempted several fixes but eventually had to move on and focus on the rest of the project.

Another issue was with the <hr> tag. It had a default border that didn’t match the design, so I had to explicitly remove it by setting border: none. Even after setting a custom color, it sometimes wouldn’t update properly—probably due to conflicting styles.

Lastly, I ran into trouble with a table where the default table borders made it tricky to apply a clean bottom border to the <td> elements. I had to reset the table styles completely and manually recreate the border layout to get the intended look.

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

I’d appreciate help figuring out why the font isn’t loading properly, despite linking it correctly. I’ve double-checked the import and usage, but it still doesn't seem to apply. I'd also love feedback on any design details I might have missed or misaligned, especially things that could make the layout more pixel-perfect.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abhijit Paul•285
    @thexeromin
    Posted about 1 month ago

    Great work bro.

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

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.

Oops! 😬

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

Log in with GitHub