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

omlette-recipe-page

Joy Abigail Mwende•10
@Unicorngal
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 am most proud that I didn't give up. This was my first coding project ever, and I pushed through despite the number of times I had to put down my laptop and take a walk to let out the frustration of errors.

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

Getting the containers and table to match the design provided. I used the Google dev editor to tinker until the design and my code matched. And deploying the project. I watched a video by KimDoesCode.

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

How did I do? Is my code readable, and clear? (In case I was working with a team, would it be good to go?) Is there an easier way to get the colors of the design? Is there an easier way to find the dimensions of the content container?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abd Ur Rehman•360
    @A-noob-in-Coding
    Posted 10 months ago

    Hi there,

    The solution appears to be too large that one need to zoom out to see the page better

    You can cover the entire recipe card container in <main></main> for better accessibility

    You can set the set the height of body to 100vh so that it covers the full screen and do not extend beyond it

    For images in html you are using the width and height in pixels instead do this

    • Try to use relative units to make the page more responsive
    • Always use the images in figure semantic tag for accessibility
    • Use the following line of CSS to make the images responsive
    img{
    width: 100%;
    height: auto;
    display: block;
    }
    

    Use the following code to make the page responsive

    I hope this comment is 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