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

Order summary card using HTML & CSS

Cody Kelly•60
@CodyKelly
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm trying to go for a more modular approach with the CSS. Someone using my stylesheet should be able to style their components by plugging in different classes in their HTML elements.

Am I succeeding in this goal? Are there any CSS classes that could maybe be broken down even further? Am I sacrificing readability and/or maintainability with this approach?

Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ivan•2,610
    @isprutfromua
    Posted about 3 years ago

    Hi there. You did a good job 👍

    keep improving your programming skills

    your solution looks great, however, if you want to improve it, you can follow these steps:

    🟢I don't think you should separate atomic classes like center-column-items and flex-end and component classes (card for example). It would be better if you followed a single approach.

    🟢try to avoid tag styling

    🟢I think it would be better to use a button than a link for the Change element. Or set the href attribute

    🟢also please set alt attributes for images

    I hope my feedback will be helpful

    Good luck and fun coding 🤝⌨️

    Marked as helpful
  • Grace•32,130
    @grace-snow
    Posted about 3 years ago

    Hi

    There are a few issues with this but all easy to fix.

    1. You need to remove the form. There's no need for a form with no inputs and only buttons
    2. Why are you using anchor tag for change and buttons for cancel and proceed? What would you expect to happen for a user on click? It may be ok, but I suspect the elements need changing
    3. You need to use min-height 100vh, not height. I'll add Screenshots to slack to show you the problems this is causing with content cropped off, and attribution overlapping content.

    I hope this is 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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub