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

Responsive Recipe Card made with HTML and Css

DoneWithWork•160
@DoneWithWork
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?
  1. Really glad that I managed to make this website responsive on both mobile and desktop
  2. Learned how to style tables a little

Would probably use SASS CSS next time to simplify CSS code or something

What challenges did you encounter, and how did you overcome them?
  1. Messy css
  2. Arrangement of layout

I watch a couple of youtube videos and use MDN docs for additional styles

What specific areas of your project would you like help with?
  1. is my css a bit messy?
  • how can I improve and write more efficient CSS
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan de Bruijn•3,220
    @DylandeBruijn
    Posted about 1 year ago

    @DoneWithWork

    Hiya! 👋

    Congratulations on your solution, it looks very close to the design! I can tell you put a lot of effort into it.

    Things I like about your solution 🎉

    • Responsive
    • Use of semantic HTML elements
    • Clear descriptive CSS classes
    • Use of CSS custom properties

    Things you could improve ✍️

    • Add a bit of padding to your body element so the card has room to breath on smaller viewports.

    • Remove the border-radius of the image on smaller viewports so it's more in line with the design.

    • Remove the wrapper <div> of the image, you can style the image directly if you want.

    • You can write this padding: 20px 20px 20px 20px; as padding: 20px; it's shorthand for the same thing.

    • You could remove the <thead> element as it's empty.

    • Try setting the font-family on the body. Other elements will inherit the font-family from their parent due to the CSS cascade. If you want to have a different font-family for the headings you can select h1, h2, h3, h4, h5, h6 and give them that font-family instead.

    I hope you find my feedback valuable, and I would appreciate it greatly if you could mark my comment as helpful if it was! 🌟

    Let me know if you have more questions and I'll do my best to answer them. 🙋‍♂️

    Happy coding! 😎

    Marked as helpful

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