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

Responsive Recipe page using CSS flex

vidyaa01•20
@vidyaa01
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 of how structured and efficiently I could think and code. Definitely practice makes perfect.

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

Following are the challenges I faced:

  1. Image alignment and fitting it in the recipe card
  2. Making the page responsive

How did I encounter?

  1. Made the image margins auto and gave it a max-width
  2. Studied media query
What specific areas of your project would you like help with?
  • When to use % and when to use px, vh etc?
  • Is there any standard way where i can learn to write neat code?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sophie•430
    @ippotheboxer
    Posted 5 months ago

    Hello, nice work with this project! The components on the recipe scale well responsively. Here are some tips!

    At full screen size, the recipe is not in the center of the page. I would recommend using flexbox to center and position divs. For example, on main in styles.css, you could add the following css properties:

    display: flex;
    justify-content: center;
    

    This will align it in the horizontal center of the page, which means you don't have to set margins and width to position it in the center. Regarding use of %, px and vh:

    VH: viewport height is usually used on the main container (e.g. body or main) and it is usually set as min-height: 100vh; to ensure it takes up the whole screen.

    px: Using pixels is usually best for setting font sizes or image width/height. You can use media query to change pixel sizes at different viewport sizes.

    Percentage: this is usually best for ensuring a div or element on screen only takes up a certain amount, for example with your component you could make it so that the img takes up 100% width, and then apply margin around.

    You also shouldn't set min or max widths to the body, but rather the custom div components such as the recipe component.

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