Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 26 days ago

Recipe Page Challenge

yekta_akhavan•170
@yektaakhavan
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 was able to do it and I'll try to do it better and faster next time.

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

I had the challenge of spacing between my list-style-type and text and dragging the table to the end of the page, but I did it by searching.

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

I'm having trouble being responsive.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,370
    @thisisharsh7
    Posted 26 days ago

    Hey, Awesome job on completing the project! 🎉

    You're already thinking like a developer by reflecting on what went well and what to improve — that's a great mindset.

    I really liked how clean your layout looks and how well-organized your HTML and CSS are. Great use of semantic tags and consistent spacing!

    You tackled some tricky parts like list spacing and table alignment — nice work figuring it out through research.

    As for responsiveness, you're on the right track! A few tips:

    • Try adding max-width: 100% to your img to make it scale on smaller screens.
    • Consider using media queries or relative units like %, em, or rem instead of fixed px sizes in some places.
    • Wrapping your .card with a container class and adjusting padding/margins at different screen sizes can help too.

    You're off to a strong start — keep exploring, breaking things, and improving.

    Marked as helpful

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub