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

Recipe page main using CSS flexbox

Ezemaolisaemeka•50
@Ezemaolisaemeka
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 proud to complete this learning part to the best of my knowledge

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

i found it difficult to position the table well, but i solved it by using the term border collapse : collapse

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • stephany247•730
    @stephany247
    Posted 22 days ago

    Hi Olisaemeka,

    You did a fantastic job on this one! The structure is clean, the design is visually appealing, and your use of semantic HTML and responsive styling is solid. 👏

    ✅ Highlights:

    • Great use of headings, lists, and semantic tags.
    • Clean and well-organized CSS with thoughtful spacing and colors.
    • Responsive layout and good use of media queries.
    • Font imported correctly using @font-face.

    🔧 Suggestions for improvement:

    • The soft pink background is showing on mobile, but according to the original design, it should only appear around the card on larger screens. Try limiting the padding or background to a wrapper element and apply it only in larger viewports using media queries.

    • Add alt text to the main image. Even a short description like "A plate of omelette" improves accessibility.

    • You could consider using semantic tags like <section>, <article>, or <header> to further structure the content.

    • The nutrition table could benefit from <th> tags for clearer headings (though this isn’t a must).

    This is high-quality work — just keep an eye on accessibility and semantics as you build more. Keep it up! 💪🔥

  • lucassalles-git•120
    @lucassalles-git
    Posted 22 days ago

    Muito bom Ezemaolisaemeka, parabéns. Ficou muito bom.

    Very good Ezemaolisaemeka, congratulations. It was very good.

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.

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