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

Responsive recipe page using flexbox

accessibility
Sean•100
@agoatnamedbear
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 that I was able to overcome a few obstacles by doing some Googling and putting it all together. Also getting the page fully responsive for all screen sizes.

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

I had a bit of a hard time with Nutrition section. I was finally able to get the right way to make the text a bit right of the horizontal rule. I also experienced a bit of confusion on how to setup the Nutrition sections HTML to utilize flexbox in the way that I intended it to. It was a bit of trial and error but I finally managed to get it done.

What specific areas of your project would you like help with?
  • HTML structure for setting up flexbox in a better way
  • Better use of semantic HTML elements
  • Making the transition between breakpoints smoother
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rowert Méndez•70
    @P0wertDev
    Posted 12 months ago

    I supose that you know now how do a better HTML structure and use CSS flexbox 😅

    However, the background color, it is not the right one 😅

    If you need some help or any question, just tell me 😁

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