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

A Recipe page using only HTML and CSS

P
Karsten Løgstrup•170
@logstrup78
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?

My mediaQueries works, that is good.

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

I had som problems separating the numbers from the text in the ordered list. I tried different things, but couldn't get it to work.

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

The above!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Levi•230
    @law973
    Posted 10 months ago

    Hi! Nice job on using a media query. In order to create space between your ordered list numbers and the list items, use a ::marker selector instead of ::before; that way, adding left padding to the li elements will create the desired effect.

    There's a few other things to mention. I think h2 should be used in place of h3; the numbers should descend based on their position in the document. If, for example, there was a subsection in the "Preparation time" section, then it would make sense to use h3 there. I would also say that the headings should be contained within the divs they belong to and not outside of them.

    Regarding the usage of semantic HTML, I like that you used the main tag. It's worth noting that all of the main content should be placed within there, which would include the image. A footer tag could be used for the attribution section, the divs within the card could use section tags, and perhaps the card itself could use its own article tag.

    It seems like the repository is private, which means the "View Code" link doesn't function properly and the code can only be inspected through browser developer tools; I would consider changing this setup for future submissions in order to make it easier for others to deliver feedback.

    I've done this challenge myself, and I know it can be time-consuming to get the details right, so I'd like to commend you for doing a solid job on the padding, text color and sizing, and using the font families in the right places.

    I hope this helps!

    Marked as helpful
  • P
    Karsten Løgstrup•170
    @logstrup78
    Posted 10 months ago

    Hi Levi. Thanks a lot for your very nice feedback. I will definitely try to use the ::marker pseudo. I'm very grateful for your help.

    Karsten

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

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

Oops! 😬

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

Log in with GitHub