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

Responsive recipe page using CSS Grid and Flexbox

vite, node
P
fringe4life•160
@fringe4life
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 am most proud of reasonably effectively getting information out of Figma in a more organised way. Checking the spacing and in this case decided to experiment with some utility classes for the spacing as the same basic spacing was used throughout.

Next time instead of simply magic numbering the spacing for the lists and the ::marker(s) I would prefer to have used the ::before pseudo element but for whatever reason I have always had a tough time using them.

Also as I in miniature made my own small utility class system it would almost be better to just go all in on utility classes vs mixing different styles of CSS together. Though, ultimately I guess i'll just learn tailwindcss v4...

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

I am not sure that ultimately this was super challenging. Though when I get to the next page and see the snapshot, I suppose i'll find out :)

Styling the table of calories etc I made overly complex using Flexbox I think 4 times, instead of just named grid areas.

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

If you are an experienced Git user I would really appreciate feedback on my use of git issues and/or commits. As I really tried to prioritise clean commits, but some really weren't.

I broke my CSS file up into multiple different files and would appreciate feedback as to how easy to grasp this is and whether I could improve this structure as I think it could be improved.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • asdiAdi•180
    @asdiAdi
    Posted 5 months ago

    You can center the recipe block by adding flex css properties on its parent.

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