Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 15 days ago

Responsive Recipe Page using Css Flexbox, media queries and BEM naming

Sean Mafnas•110
@Makkatlahi
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 proud that I was able to approach this in a mobile-first manner. Adjust the styling according to the dimensions was tricky, but I found it to be a little less troublesome when going from desktop to mobile.

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

I had a few challenges that forced me (in my current skill level) to utilize more specific manipulation of the styling components. I didn't want to break up the original structure of the html because I thought it would disrupt the layout and styling of the mobile view. I decided to tweak the surrounding properties of the property I was trying to correct.

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

I would like help with coming up with better styling practices that allow me to avoid having to explicitly manipulate a particular property in order to achieve the desired result. I felt this was analogous to 'hard coding' values instead of passing in ones received from user input.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,410
    @thisisharsh7
    Posted 15 days ago

    Great job on the Recipe Page! Your mobile-first approach is commendable, ensuring a solid foundation for responsiveness.

    • The clean HTML structure and use of CSS custom properties (e.g., --Stone-100) enhance maintainability.

    • To improve styling practices, avoid hard-coded values like width: 200px or width: 136% in favor of relative units (e.g., vw, rem, or %) or CSS calc() for dynamic sizing. This reduces specificity and makes adjustments easier.

    • Consider using CSS Grid for the main layout to simplify alignment and spacing, reducing reliance on manual tweaks.

    • The media query range (500px–1580px) is broad—add intermediate breakpoints (e.g., 768px) for smoother transitions.

    • For the image, use aspect-ratio to maintain proportions instead of fixed heights.

    • To level up, explore SASS for nesting or Tailwind for utility-first styling. Strong work—focus on relative units and modular CSS for more flexible, scalable designs!

    Great work overall- Happy coding!

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