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

Responsive recipe page using media queries

Abdul-Saidat•50
@Abdul-Saidat
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 tried this same challenge when I started coding last year and it was nothing close to the design, working on it again made me realize how much I have improved in less than a year

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

None

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

I need reviews to know where I still need to improve

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mustafa Sen•3,180
    @mustafasen97
    Posted about 1 month ago

    The design is great. It was a good idea to create a responsive design using the media tag.

    There are a few points you can improve in the code structure.

    Your HTML is not too bad in terms of semantics, but instead of using too many divs, you can prefer semantic tags like section and article. You can research semantic HTML and try to practice on this subject.

    Semantic HTML Example

    
    <body>
      <header>...</header>
      <main>
        <section>
          <article>...</article>
          <article>...</article>
        </section>
        <aside>...</aside>
      </main>
      <footer>...</footer>
    </body>
    
    

    Apart from this, it would be better for you to set the class names in HTML more meaningfully and properly. In this way, you can prepare the design in a more practical way. I recommend you to research BEM to improve yourself on this subject.

    BEM (Block, Element, Modifier) ​​is a naming methodology that makes it easier to write consistent, readable, and maintainable code in large-scale CSS projects.

    BEM Example

    <article class="product-card">
    
      <img class="product-card__image" src="product.jpg" alt="product">
      <h2 class="product-card__title">Product Title</h2>
      <p class="product-card__description">Description</p>
      <button class="product-card__button product-card__button--buy">Buy Now</button>
    
    </article>
    
    

    Another thing I want to talk about is variables. Before moving on to coding in CSS, you can define some variables, assign colors, font sizes, font weights and many more things that you will use frequently in the design to these variables. In this way, you will reduce code repetition. Keep improving yourself. Good luck.

    Variables

    variable definition
    
    :root {
      --bg-color: hsl(217, 54%, 11%);
      --card-color: hsl(216, 50%, 16%);
      --text-secondary: hsl(215, 51%, 70%);
      --text-primary: hsl(0, 0%, 100%);
      --accent: hsl(178, 100%, 50%);
    }
    
    variable usage
    
    body {
      background-color: var(--bg-color);
    }
    .value {
      color: var(--accent);
    }
    
    
  • Jorge Rosales•50
    @Junkdog-04
    Posted about 1 month ago

    Hey! Nice job on the project! 👏

    One suggestion: consider using the custom fonts provided in the project files to better match the design. It’s a great opportunity to practice loading local fonts with @font-face.

    Also, try using more semantic HTML tags like <main>, <section>, <article>, and proper headings (<h1>, <h2>, etc.). This not only improves accessibility but also helps with SEO and keeps your structure clean.

    Keep it up — you’re doing great! ✌️😊

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