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

Showkat/my-recipe-page-solution

showkat219•40
@showkat219
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • beowulf1958•1,890
    @beowulf1958
    Posted about 1 month ago

    Congratulations on completing this challenge. Your html is clean and clear and the styles are easy to understand. The box-shadow is awesome: subtle but effective. You have picked up on the color change on the list bullets and correctly used ::marker. (however you missed that the numbers on the ol are also orange) <ol class="orange-bullets"> Also I like how you used table th:nth-child(2) to target the numbers. I do have a few suggestions.

    First, the image is not showing up due to an incorrect file path. The jpg is in the root folder and you are directing the browser to look in a subfolder called assets. The correct path is <img src="image-omelette.jpeg" alt="Omelette" class="recipe-image"> Second the Nutrition heading is not showing up because the h2 opening tag is missing a bracket. You have <h2 style="color:hsl(14, 45%, 36%) ;" Nutrition></h2> which should be <h2 style="color:hsl(14, 45%, 36%) ;"> Nutrition</h2>

    Next the table does not have a border-bottom in the design. To fix this add a style to the las two th

    <th style="border-bottom:none">Fat</th>
    <th style="border-bottom:none">22g</th>
    

    I also think you should consider giving the body element a background-color to better distinguish the card from the page (maybe Rose 50: hsl(330, 100%, 98%) ?)

    Again, great job and keep on coding!

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