Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

first-project-responsive-order-summary-using-grid, only html & scss

Novidicus Titan•60
@NovidicusTitan
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have made a video about how i did this project on my youtube chanel if you want to check it out, thanks

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ken•4,915
    @kens-visuals
    Posted over 3 years ago

    Hey @NovidicusTitan 👋🏻

    I've got some suggestions to help you fix the accessibility and HTML issues.

    • In your markup, <div class="">...</div> should be <main class="">...</main> and <div class="attribution">...</div> should be <footer class="attribution">...</footer>.
    • Next, you cannot nest button inside <a> tag or vice versa. In this case you have to choose between one of them.
    • Next, I suggest using <h2> or <p> instead of <h4>, because headings in HTML have to increase gradually, such as h1, h2, h3….. These will fix the accessibility and HTML issues. Don't forget to generate a new repot once you fix the issues.
    • For the music icon, add aria-hidden="true”, because it's for decoration. You can read more about aria-hidden here.
    • Hero image should have a display: block;, it removes the line underneath the image. If you want to know what's causing it, check out the 3rd section of this video.
    • Also, I suggest adding transition: all 0.2s; to the button and the links, this will make :hover smoother.
    • Lastly, I won't go into many details about resetting CSS, but I'll leave this cool article here, which will make more sense than my brief explanation.

    I hope this was helpful 👨🏻‍💻 all in all, you did a good job for your first project, nicely done. Cheers 👾

    Marked as helpful
  • Saurav Singh Khekhaliya•190
    @sskhekhaliya
    Posted over 3 years ago

    hey, I just looked at your site, there are some suggestions:

    1. There is no need to using border-radius: 20px 20px 0px 0px; for image, instead of it just apply overflow: hidden; to .container. So it will hide the corners of images also.
    2. It will be good to give a little padding-bottom to the card.
    3. Card's margin-top:40px; didn't make it vertically centered and if someone will see your site on the big screen then the card is not able to be vertically centered. So for it, you can use display: flex; for body and then set its direction to column (flex-direction: column;) and give a height to the body 100vh.
    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 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