Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Order Summary

Sarah T•70
@sarahtazyan
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How can I add the shadow on the button with the exact color and design that is shown in the preview? Thank You

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Atif Iqbal•3,320
    @atif-dev
    Posted almost 2 years ago

    Hi, congrats🎉 on complleting the challenge. Better take care about following points:

    • For better look on larger screens modify code as:
    body {
      background-image: url("images/pattern-background-desktop.svg");
      background-repeat: no-repeat;
      background-size: 100%;
      background-color: hsl(225, 100%, 94%);
    }
    
    • For button shadow add box-shadow: 0px 18px 17px 0px #DFDCF9; in button selector instead of box-shadow: 0 1px 2px rgba(0, 0, 255, 0.5);
    • When we open GitHub repository link, at right side you will find an About Section. There, also include live preview link of your project. It is better for someone to check your live project while interacting with code.
    • In README file of your GitHub project's solution: write about your working flow, findings, new learned things, useful resources, etc.

    Hope you will find this Feedback Helpful.

    Let's connect for learning📝 and sharing🤝. Twitter , LinkedIn

    Marked as helpful
  • Boots 😺•1,610
    @adityaphasu
    Posted almost 2 years ago

    Hello, @sarahtazyan!

    • Firstly to get that background bluish color like in the design it can be achieved using background-color property on the body like this:
    body{ 
        background-color: hsl(225, 100%, 94%);
    }
    
    • For the box shadow on the button I tried some values in the devtools and this is what I found to be closer to design:
        box-shadow: 0 4px 13px rgb(64 64 242 / 50%);
    

    Some suggestions to improve the code:

    • Instead of using absolute position to center the card you can use flex properties on the body instead like this:
    body {
         min-height: 100vh;
        display: flex;
        justify-content: center;
        align-items: center;
         //rest of the styles
    }
    
    • This will center the card in the middle of the page and you can remove:
    .box-container {
        position: absolute;
        top: 50%;
        left: 50%;
        transform: translate(-50%, -50%);
    }
    

    from the .box-container.

    Keep up the hard work and good luck!

    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