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

Recipe page using HTML and CSS with flexbox

Antony Checo•130
@acheco
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Petter Torst Saatvedt•180
    @PetterTSaatvedt
    Posted 6 months ago

    Great work on your solution Antony! It works well for both desktop and mobile screens, and you have done a great job in adapting the image for both designs.

    Not much to complain about here! However, here are a few tips which could make your solution even better:

    • H1 tags are typically reserved for the singular most important heading on the page, and should therefore only be used once. Consider changing all headings to H2 tags, except for the "Simple Omelette Recipe" heading which can stay as an H1.
    • Try to avoid using px as a unit for font size. Since this is a fixed unit, it is not scalable for users who want to make the text bigger or smaller. I would recommend using a responsive unit like for example rem, where 1rem is equal to the root font size (which is 16px by default). This will allow for better scaling of the font size.
    • As the solution includes a lot of information/text, it is important to provide sufficient spacing to let the content "breathe". I would suggest to revisit the design and follow the suggested spacing approach.

    Nonetheless, your code is perfectly readable and easy to understand, and the solution looks great! Keep up the good work :-)

    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 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