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

Recipe Page using Flexbox and @media CSS rule

Ryan O'Hanlon•140
@Ryan-OHanlon
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?

What I'm most proud of for this challenge was being able to quickly structure the framework for the HTML file. I'm able to quickly know which elements to use to create ordered and unordered lists and know when to use a table. It didn't take much time for me to structure the text with the appropriate html tags.

If I could do something different, it would be to build a better understanding of responsive web design and understand the CSS attributes for each html element. I'm still having trouble ensuring that the desktop width matches the design document and while I understand flexbox, adjusting the margins and padding for all the html elements makes it hard to know if I'm creating an exact replica of the challenge.

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

One main challenge I had was making the image take up the same width as the rest of the webpage when the width of the webpage was at 375 pixels.

The challenge was making two sets of CSS rules using the @media rule and adjusting the body and main properties to have the appropriate margin and padding when the webpage surpassed 375 pixels so the image will have a border radius and white section.

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

I would like help with knowing how to figure out how to use margin and padding so that the desktop design matches the design document while being responsive. I don't know how to make the width of the main element be an exact match to the design document.

The other issue I had with this project was the colors for the style guide. There were eight colors for this challenge, and I could only determine four colors. Even using a color picker did not match the hsl values as provided by the style guide.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ryan O'Hanlon's solution.

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.