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

Recipe page

Sabina•10
@SabinaZus
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 the fact that I still remembered most of the basics of HTML although I learned it 2 months ago for only two weeks.

Next time I would probably clean/delete some unnecessary code regularly throughout coding. Only by the end of making finishing touches I noticed there were some lines that didn't have to be there. It simply started piling up and at one point it started to be a bit chaotic and unclear.

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

I had difficulty including the last section of the recipe card (Nutrition) into the rest of the card. It was standing alone from the rest and it took me awhile to figure it out. Eventually I noticed that the case sensitivity was the issue the whole time and it solved the whole problem.

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

Is there a simpler way to code the responsive design for other devices? Although my way works I feel it's a bit cumbersome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Łukasz Gwarda•180
    @lgwarda
    Posted 8 months ago

    Hi there! Here are three handy tips for a smoother responsive design workflow:

    1. Flexbox is Your Friend If you're looking for an easy way to create a one-dimensional layout (either row or column), Flexbox is a great tool to have in your CSS arsenal. It can help make your designs more adaptable across different screen sizes.
    2. Choose Relative Units When it comes to units in CSS, try using relative units like em, rem, %, or vh/vw instead of fixed pixels. These units can adjust according to the screen size, making your designs more responsive and saving you time in the long run.
    3. Think Mobile First A great approach to responsive design is to start by designing for mobile devices. Once you have your mobile design down, you can then use media queries to adapt your design for larger screens. This keeps your CSS simpler and more organized! Hope these tips help you out!
    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub