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

HTML and CSS and some media query. one inner style.

Buddyyy•40
@semi26
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


All feedback are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • IRVINE MESA•1,835
    @DrMESAZIM
    Posted about 3 years ago

    Hi @semi26

    I noticed that there is need to remove some text decoration on the following classes

    btn btn-change btn btn-change

    To do that simply add this property on line 6 inside the file style.css

    text-decoration:none

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted about 3 years ago

    Hello there, Raul! 👋

    Congratulations on completing your first Frontend Mentor challenge! 🎉 Your solution looks pretty good! Also, well done on leaving the alt empty to all decorative images! 👏

    There are still some things that can be improved.

    • I highly suggest never using inline styling. It's not reusable and hard to maintain. Also, it has very high specificity. So, my recommendation is always to put all the styling into the external CSS.
    • Always specify the type of the button. In this case, set the type of them as type="button". It's going to prevent the button from behaving unexpectedly.
    • On mobile view (375px width) I recommend adding some padding on body to prevent the card from touching the browser's edges.
    • Create a custom :focus-visible styling to any interactive elements (button, links, input, textarea). This will make the users that navigate this website using keyboard (by using Tab key) know where they are on the page.

    I hope this helps! Keep up the good work! 👍

    Marked as helpful
  • Kamasah-Dickson•5,570
    @Kamasah-Dickson
    Posted about 3 years ago

    Your card is covering the whole screen on smaller devices, give a margin left and right on smaller devices to avoid your card from spanning the whole screen.

    • there is also so much box shadow on the button.
    • you also forgot to add a box shadow to your card.

    Besides good job👍 Keep coming👍

    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

Oops! 😬

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

Log in with GitHub