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

CSS flexbox

Ademuyiwa•200
@codingat17
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I couldn't get the background-color for desktop sizes and also the image, the border-radius property didn't work well with it

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • 5nufkin•60
    @5nufkin
    Posted 7 months ago

    Hi there, Good job on this one, your website seems responsive and looks good! One thing I noticed right away was the body background color that's not exactly what you were asked to do, consider fixing this. About your html file - for better readability and structure, consider adding a header and a footer - in the header you could include the image and name of the recipe, then in main the recipe itself and in the footer you could put your note - "challenge by frontend mentor..." Also, consider naming classes in a more meaningful name that would help understand your code, c1, c2 and so on doesn't really deliver the message on what exactly this class is about. In addidtion, consider using sections and ids as well, ids are used for elements that you only have one of in your code, for example you could replace the c2 div with a section tag, it would look like this: <section id="preparation-time">....</section/ That would make your code much more readable. Your CSS looks good and it looks like you took a mobile-first approach which is a great way to design these days, very good! I hope this was helpful, keep going - you're on the right track!

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

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