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

Order summary component

Paulo Ricardo•140
@PauloRicardoSM
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


To place the card in the middle of the screen I used the value "display grid" and "place-items: center" in the body, but I notice that on small screens (mobile), the card is a little further to the right. Can you give me any suggestions on how to leave it in the middle, regardless of the screen size? (Sorry if I didn't explain it very well).

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • MaximilianoDanielGarcia•1,980
    @MaximilianoDanielGarcia
    Posted almost 2 years ago

    Hi Paulo Ricardo, good job!

    I think the error you are referring to is because you have a margin on body tag, just add margin: 0; and that's it. Also, for improve your body's background try this:

    body {
        background-image: url(../images/pattern-background-desktop.svg);
        background-repeat: no-repeat;
        background-size: contain;
        background-position: center top;
        width: 100%;
        background-color: hsl(225, 100%, 94%);
    }
    
    
    Marked as helpful
  • Laura Ortega•100
    @Pancratzia
    Posted almost 2 years ago

    Hi, Paulo! I've reviewed your code and found that your problem is that you're using width: 100%; in your body tag. If you delete that line, your code works fine! Also, try using this snippet for box-sizing. It'll help you in your future projects with box model sizing, which can be a nightmare sometimes!

    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