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

Responsive Omelette Menu

José Mama•240
@codesByJose
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?

made the required adjustments!.. this was one difficult task for me, but im glad it pulled through.. pls do leave your thoughts concerning this

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Arinze Owoh•150
    @ArinzeGit
    Posted 9 months ago

    I sent an initial comment but I’m just realizing it didn’t send (that’s why the second comment began with “also”). I’m gonna send it again now. Here it goes:

    Jose mama! Agba dev! You’re doing well. For future projects try to follow the design spec more closely e.g font family, font size, font color and layout so that the comparison slider will be more matching. You got this💪🏽

    Marked as helpful
  • Arinze Owoh•150
    @ArinzeGit
    Posted 9 months ago

    Also. I suggest you add a README file to the GitHub repo of this project. You can use the template provided in the challenge repo you got from frontend mentor upon starting the challenge. The template will guide you to add overview ,screenshots, link to live site, what you learned, continued development, useful resources, author… An informative README that provides context is always nice for a GitHub repo. Keep pushing💪🏽 you got this.

    Marked as helpful
  • Mohammad-Moneer•120
    @Mohammad-Moneer
    Posted 10 months ago

    Hello there, You made a good solution 👍 Your code is well-structured and easy to read.

    Suggestions for Improvement:

    • The use of HTML5 semantic elements (<section>, <h1>, <h2>, <h3>, <ul>, <ol>, <table>) is good. However, wrapping the content inside multiple <div> elements instead of using more semantic tags (like <main>, <article>) can be improved for better readability and SEO. For example: You could replace the element <div class="container"> with <main class="container"> and also the element <div class="innerCont"> could be <article class="innerCont">

    • The width of the <div class="container"> should be larger to match the design.

    • The font size of the headings and body text should be adjusted to match the design.

    • The image dimensions are explicitly set with width="320px" and height="130px", which might distort the image. It's better to use CSS to set a width of 100% for responsive designs.

    Overall, your project is well-structured and follows a clear layout. I hope you find these suggestions helpful.

    Marked as helpful
  • Supa-Thobile2•100
    @Supa-Thobile2
    Posted 10 months ago

    The code base is easy to read and follow.

    The design could be greatly improved with margins and padding.

    The design is close to the one on design assets but it could be improved.

    The readability of text on the small screen is a strenuous exercise. The fonts can be increased for better readability.

    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

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

Oops! 😬

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

Log in with GitHub