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

Responsive Recipe Page using HTML/CSS

Dias•140
@adambeckercodes
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’m most proud of creating a clean and responsive recipe page with accessible features like semantic HTML, and focus-visible styles. The use of CSS variables made the styling consistent and easy to maintain, and the design adapts well to mobile and tablet devices.

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

Responsiveness: Adjusting the layout for various screen sizes was tricky, especially balancing spacing and font scaling for mobile and tablet devices. I overcame this by using a mobile-first approach and testing with multiple media queries. Still there are some things which don't work as intended.

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

Feedback on adding animations or JavaScript for a more engaging experience would be great. Are there any specific features I could implement to make the page stand out?

Is there a more efficient way to build this kind of layout?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • why-not-phoenix•330
    @why-not-phoenix
    Posted 7 months ago

    Hi dias!! Once again another near perfect solution. I have a few questions:

    1. In line 36 to 47, why did you have to specify box-sizing: border-box; for the html? wouldn't it have same effect if it were * {box-sizing: border-box;} instead of inherit?
    /* GENERAL */
    html {
      box-sizing: border-box;
    }
    
    *,
    *::before,
    *::after {
      box-sizing: inherit;
      margin: 0;
      padding: 0;
    }
    
    1. What is the function of body { height: 100vh; } ? Wouldn't the content just overfow?

    I probably have other questions but I am sure you're too busy for them. Great solution, looking forward to more of your solutions.

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.

Oops! 😬

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

Log in with GitHub