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

Order Summary Card

Tyra Carter•20
@teecarter16
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I was struggling with the box-shadow, any tips are appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Julian Krüger•100
    @juliankruger
    Posted over 3 years ago

    Hi Tyra,

    nice job on the challenge, looks good!

    Regarding the box-shadow: The challenge presented a very subtle shadow and your solution is already on the right track. There are four values: the first value, x-offset is 0, because you only want to push the shadow down a bit, not to the side. The second one is the y-offset, which pushes it down. That is correct.

    Then the blur-radius and the spread-radius become important: A nice tip for a subtle box-shadow is a negative spread-radius. Your fourth value, the spread-radius, is 0, you could try a negative value, like the same or half of the third value and adjust the second and third values along the way. Try around a bit, you also used two colors, maybe try it with one first.

    Another tip: You can look into the report on the solution page, it tells you about HTML and Accessibility issues. It might seem like a lot at first but there are usually easy fixes and there is a lot to learn about HTML structure and Accessibility. This site takes great care of you in that regard. (One easy fix, for example: You replace the bottom div-tag with a footer-tag)

    I hope that helps, have a nice day! :)

    Greetings!

  • P
    David Turner•4,130
    @brodiewebdt
    Posted over 3 years ago

    In the Figma file the settings are: box-shadow: 0px 40px 40px -20px rgba(13, 48, 189, .15)

    Add alternate text to your images. It can stay empty since they are decorations. Wrap your card div in a Main tag, change the Order Summary to an H1. You may have to re-style it to look the same as in the design. Change the attribution div to a footer and it will clear the accessibility warnings.

    Download AXE DevTools and you can clear accessibility warnings while you code. https://www.deque.com/axe/devtools/

    Hope this helps.

  • Robert Rynard•560
    @Robert-Rynard
    Posted over 3 years ago

    What did you feel you were struggling with the box-shadow? If you are trying to have more shadow on the bottom and less on the side you can use a negative spread-radius to bring in all sides and then move it further down the y axis.

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