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

Omelette recipe page made using CSS and HTML

BegShoo•80
@BegShoo
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 think I got the rough layout, sizing and sections mostly correct. It was a challenge without the figma file but just feeling out the site and double checking the colors got me most of the way there.

Next time I think I'd pick my own recipe and do that. I might include some pictures of steps when making the food, or even of the ingredients. That would add another layer of complexity.

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

I had trouble with the tables because I don't use it much, and also some issues with the counter and the text dipping underneath it.

Initially I used divs in a grid and it turned out okay, the only issue then being that it wouldn't be semantically coded, and also it's possible with counters and ol and li elements, but it did take me a lot of research and checking other peoples solutions to figure them out.

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

Checking the tables would be great, also checking the ol and the li and the absolutely positions counters before would be great. I think this is the correct solution that retains the semantic elements, but I'm also not entirely sure it's done right!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vandorpe Jentl•50
    @VandorpKe
    Posted about 1 year ago

    I don't really see the use for counters yet. For example if you wanted the numbers in the instructions list (1. / ... / 6.) then 'ol' does that automatically. If you wanted to change the collour or something you better could've used the 'li:marker'. This would've targeted the marker that you wanted to change. Hope this helps! If not, ask away.

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