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

Recipe page css html flex box

accessibility, cube-css
aman kumar•720
@amankumar1222
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?

Hi my name is aman kumar i am learning web development now my focus to learn js so please help me to learning

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

it's simple

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

in responsive

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rahul Kumar•570
    @rahulkumar215
    Posted over 1 year ago

    Hello @amankumar1222👋

    Congratulations on successfully completing the challenge! 🎉

    I have a suggestion regarding your code that I believe will be of great interest to you.

    • in Nutrition section, You have set

            <tr>
              <td>Calories</td> // black color
              <td>277kcal</td>
            </tr>
      

    however, in design it's actually var(--neutral-wenge-brown);, so you might want to set it

    td:first-child{ color: var(--neutral-wenge-brown); }.

    Its just a slight improvement, but I hope it helps.

    • You have also set the border at the last child of the table as well, where in design its not there

    so instead of this

    td { border-bottom: 1px solid #ddd; // this one }

    you should use this

    tr:not(:last-child) { border-bottom: 1px solid #ddd; }

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    If you need any feedback or suggestions, I am happy to help

    Have Fun Coding!

  • aman kumar•720
    @amankumar1222
    Posted over 1 year ago

    Thanks bro and i will update my solution soon

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