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

Responsive Recipe page

agnese•360
@aggie-l
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 of finishing another challenge, although there are probably better ways of doing it.

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

One of my main challenges so far has been centering the main component - in this case the recipe page container - right in the middle of the page. I have tried using flexbox before, I am using grid here, but for some reason I don't understand it is not centering properly. Also, I used padding on body to prevent the recipe container from sticking to the top and bottom of the page.

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

All feedback is very welcome and appreciated :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Moses•340
    @mbtenkorang
    Posted about 1 year ago

    @aggie-l Congratulations 🎉🥳👏 on completing this challenge.

    Some feedback in relation to the challenge you encountered;

    • To notice that your design choice for the <body> element works you may view the webpage in the browser on a simulated 4K display using the Toggle device emulation feature - CTRL+SHIFT+M of the Developer console - CTRL+SHIF+I.

    • A quick fix though, for mobile devices the <body> element receives a padding which based on the designs will be more suitable only in a media-query for desktop/larger displays. The padding should keep the page "centered" until the display is much much larger as you've done now.

    • The flex declaration for the .recipe-container can be removed and the design will still hold because the padding value of the .recipe-container is keeping all the elements in line at the along all edges

    I hope this feedback helps. Great job 👍and happy coding 😁🧑‍💻

    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