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

Recipe page using responsive design

P
skhbabez•60
@skhbabez
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 enjoyed working out all the different stylings for the lists, tables and the image, since they provided unique challenges. But next time I will try to utilize simpler solutions, since i felt like I overdid it a little, even though I learnt a lot of new css tricks from this. I will also try to come up with a better class strategy, trying to avoid overusing css selectors like I did here

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

Styling the image was challenging, making sure it stays responsive between the different screen sizes. Using aspect-ratio and an image wrapper made this easier though. Centering the text on the lists and getting the spacing on the table right was difficult, but using pseudo-elemnts above ::marker helped to solve these issues. The solution with counter is probably overkill though and ::marker probably would have been enough here.

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

Any Ideas on how to apporach spacings in lists around the bullet points and text alignment without using anything more complex than ::marker.

.card :is(ul, ol) li {
  display: flex;
  gap: var(--space-4);
}

.card ul li {
  align-items: center;
}

.card ul li::before {
  content: "";
  width: 4px;
  height: 4px;
  border-radius: 50%;
  background-color: var(--brown-800);
  flex-shrink: 0;
}

Also, I can't figure out where the size difference is coming from between my preparation section nad the solution

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shreya Banerjee•40
    @ShreyaB001
    Posted about 1 month ago

    Learn lot of new things

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