Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 months ago

An Order Summary built with HTML/CSS

Wisdom Ebong•170
@wisdom-ebong
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • echo-script0•180
    @echo-script0
    Posted about 2 months ago

    Hi Wisdom. I recently finished this project,i noticed a couple of fixes your project needs if you don't mind. First, the background image is not quite right, it's the other way around Second, the hover state on the change link is not visible on the live page Third,The background color for your proceed to payment container is not the same as the style-guide Lastly, the cancel order element has a couple of things wrong with it( the color, the container- it's not supposed to be in a container, and the hover state is also wrong. Let me know if you need help with anything and i'll be glad to help. Bye!

    Marked as helpful
  • Vladimir Miljkovic•460
    @miljkovic5
    Posted about 2 months ago

    Nice work! The layout is clean, visually appealing, and responsive. Great use of shadows, border-radius, and hover effects to bring the component to life.

    That said, one key improvement you could focus on is switching to a mobile-first approach. Right now you're overriding base styles with @media (max-width: 600px), which is less efficient and opposite of what most modern CSS frameworks and design systems (like Tailwind, Bootstrap, etc.) recommend.

    Start with your mobile styles as defaults, then scale up using min-width media queries. It’ll keep your CSS leaner and more maintainable.

    Keep it up — you’re really close to a production-grade setup! 📱➡️🖥️

    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

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