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

Responsive Recipe Page with HTML and CSS

P
Dexter Niles•140
@dexterniles
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?

This is the first time that i've had to make a website that adjusts for desktop and mobile viewing. I went through many iterations trying to get it right and honestly I don't think that i've gone about it in the best way but it works. Using media queries definitely gave me a run for my money but it turns out i was just overcomplicating things.

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

Media queries really got to me but in the end I think I have it figured out on a basic level. Definitely still have a lot of learning to do but this helped me jump through a lot of hoops that I was struggling with.

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

Specifically how to write out media queries. I wasn't entirely sure what i should include in them. I have basically my entire css copied into a media query but I have a feeling that all i need to include is the parameters that I changed to make it work instead of all of the CSS code. I would really love some feedback on that and anything else that you find is a little wonky.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Akiz-Ivanov•450
    @Akiz-Ivanov
    Posted 3 months ago

    Media queries help make webpage look good on all screens, for example if you have a rule that you want to apply only on large (desktop) screens you can set:

    @media (width > 1024px) {
     /* If the width of the browser window is 1024px or larger, apply these styles */
    }
    

    If you pasted all the code in media query, you can delete it, because it's already applied to all screens if it's declared outside of the media query.

    Example of how the media query is used:

    Let's say you set padding: 10px on main, but on larger screens you need bigger padding to make layout look good:

    main {
       padding: 10px;
    }
    
    @media (width > 1024px) {
       main {
            padding: 20px;
    }
    

    On screens smaller than 1024px <main> will have 10px padding and on screens larger than 1024px it will have 20px padding.

    It helps to make site responsive on all screen sizes.

    You did brilliant job on the challenge, keep it up.

    Marked as helpful
  • Karannn3011•610
    @Karannn3011
    Posted 3 months ago

    Great job, Dexter! The thing which can help you out in media queries is starting with mobile view first. The design doesn't "breaks" when you're scaling things for larger viewports - so it's easier starting from mobile working on larger width in media queries.

    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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub