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

recipe-page-main

Azhel•120
@Azai4
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 went out of my comfort zone to solve a big challenge, try to make it on accessible to the mobile view

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

I encountered the challenge of positioning and overvcame them by checking for solutions on google

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

in making it accesible to mobile view

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•7,170
    @MarziaJalili
    Posted 4 months ago

    Hey there!

    Here's the answer to your question:

    I reviewed the code and figured out you hadn't used media queries.

    Media queries are essential for creating responsive designs that adapt to different screen sizes, especially for mobile devices.

    Here’s a basic code of how to implement them:

    @media (condition) {
      /* CSS rules here */
    }
    

    In the condition you are required to set some breakpoints.

    • By setting this media in your code you'll make the code responsive for mobile, too:
    @media (max-width: 30em) {
    /* set a fixed width for the section so it doesn't overflow */
      section {
        max-width: 300px;
      }
     
    /* ensure that everything nested inside also has the same size */
      section > * {
        max-width: 300px;
      }
    }
    
    • Also, get rid of lines 154 and 143 in style.css that has the code (flex-wrap: wrap;). It's causing some overflow issues, man.

    • Finally, set the code below for the image to prevent it from overflowing:

    .header img {
      max-width: 100%;
    }
    

    This definitely works!

    In case you find any difficulties, let me know.

    😎😎😎

  • Leoy96•120
    @Leoy96
    Posted 4 months ago

    Awesome

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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