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

order-summary-component-main

Sultan Hafizh Alexander•30
@shalexandeer
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


how to add button shadows in proceed payments?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • lr6kidy•280
    @lr6kidy
    Posted about 3 years ago

    Hi!

    I think the spreadSizes of your button's box-shadow (the fourth value, in your case, -30px and -20px) are way too low considering the size of your button. Try 0, and chances are a shadow will appear, you can then change it from there.

    Also, don't forget there are active states to the buttons and the "change" link. And you can set the background-color of the body to the light blue color listed in the style guide so that underneath the wave isn't white, and it matches the design.

    Good luck!

  • Mo•840
    @MohamedAridah
    Posted about 3 years ago

    Hello ,

    • for .parent you need to add background-color property to to add background for the element and make it like the design.

    • for .parent there is no need to use fixed height. height: 560px.

    • for .parent to make the waves illustration looks closer to the design you can change background-size property to 100% instead of cover. or you can remove background-size property at all. you cab read about background-size from Here.

    • So after all this changes to the .parent it's styles will be like this:

    .parent {
        display: grid;
        place-items: center;
        min-height: 100vh;
        background: #e0e8ff url(../images/pattern-background-desktop.svg) no-repeat;
    }
    
    • for .container you can remove margin-top property if you want the card to be perfectly centered.

    • Don't use fixed height let content itself determine it's height. so you can remove height: 335px for .card-content div

    • for card-title instead of using <h2> heading level use <h1> heading level instead. This will fix your Accessibility issues as well.

    • when you use width: 80% instead of using margin-left or margin-right to center the content . You can just use margin: auto.

    • use font-family globally in the body for example instead of redeclare it for each element

    • .pay and .cancel have common styles so you can combine them in one class and add it to them instead of redeclare it again.

    • for your question you can see My solution for this challenge it may be helpful for you..!

    I hope this wasn't too long for you, hoping also it was useful😍.

    Goodbye and have a nice day.

    Keep coding🚀

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