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

Order summary component with vanilla HTML, CSS.

Sebastian Arevalo•130
@arevalosebastian
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Always happy with feedbacks :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hi, Sebastian! 👋

    Nice solution! It's great that you are using the main element to wrap the card content. It's also a good thing that you are wrapping all the interactive elements with interactive elements, in this case, with button elements.

    However, I have two things that I would like to suggest,

    • Firstly, I would recommend fixing all the accessibility issues that have been reported by Frontend Mentor. Having an accessible is one of the most important things that you need to consider as a frontend developer. You could click the Learn More link to get more information about the issue and how to solve it.
    • Second, I would suggest specifying the type of any button elements. By doing that, you will prevent the button from behaving unexpectedly, like submitting. In this case, you can specify the type of them as type="button".

    Overall, you have done a great job with the HTML markup and I think if you fix all the accessibility issues, it would make your website more accessible to more people, especially for the people who rely on assistive technology. 😉

    That's it! Hope you find this useful! 😁

    Marked as helpful
  • Travolgi 🍕•31,300
    @denielden
    Posted over 3 years ago

    Hi Sebastian, I took some time to look at your solution and you did a great job!

    Also the top background image is broken because the url is incorrect, fix it like this: background-image: url(../assets/images/pattern-background-desktop.svg); to body and try to add a little transition on the element with hover effect

    Overall you did well 😉 Hope this help

    Marked as helpful
  • Abdo Arafah•70
    @AbdoArafh
    Posted over 3 years ago
    • You can make Order summary bold
    • don't set a max-width on the img a width: 100% would be a good idea in your case
    • the lower part of the card needs more padding
    • the annual plan part needs a background color
    • Please, Don't have a set width on the card it self or just increase it

    Overall the design looks fantastic. I hope you do even better next time ;)

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

Oops! 😬

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

Log in with GitHub