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

Summary card using flexbox

Tobiasz•270
@tobiasz121
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was my first project done on my own. Any feedback always appreciated. Got a little confused about how to organize my css file and what classes, selectors etc. should I use.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Remus D. Buhaianu•3,125
    @remusbuhaianu
    Posted over 3 years ago

    Congrats on completing the challenge on your own, @tobiasz121!

    I had a look through your Github repo and final solution and I have a few suggestions that I hope will be useful to you:

    • Your card's dimensions are a bit too big

    • You used the wrong color for your button's box-shadow

    • You should more meaningful class names in your HTML

    • Add more classes in your code. There are a lot of HTML elements that don't have any class on them

    • No need to set a fixed height on the main element

    Marked as helpful
  • nikbos•30
    @nikbos
    Posted over 3 years ago

    You can use <a> tag for Change and Cancel Order <button> for Proceed to Payment

    Use @media

    You use the wrong box-shadow color at line 170.

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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