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

Trying to solve order-summary-component

mandresy andri•90
@mandresyandri
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I know we are not saturday but I finished the challenge earlier that It seems. 🙂

You can see here my solution. Do not hesitate to leave a comment if you have some advice or code improvement. I'm open for all feedback. 🙃

Can you tell me what challenge can I do next ??

Thank you all !

Have a nice week ! 😉

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • javascriptooo•310
    @javascriptooo
    Posted about 3 years ago

    Hi there!

    In your report, you are having 5 accessibility issues and 2 html issues.

    To resolve them, add an alt text attribute to each img tag (html);

    For accessibility, you always need to insert a landmark tag within the body. I would insert a <main> landmark tag around the contents of the webpage. Here is some [documenation](https://www.w3schools.com/accessibility/ accessibility_landmarks.php.)

    Also, try adding to the body selector in your css: height: 100vh; That should center the flex container from top to bottom.

    Nice Work! Hope that helps!

    Steven

    Marked as helpful
  • Ismail•230
    @itbeginswithi
    Posted about 3 years ago

    Hi Andri, congrats on finishing your latest project.

    To center your card, you can use absolute positioning. To try it out, add the following css lines to your container class:

    position: absolute; top: 50%; left: 50%; transform: translate(-50%, -50%);

    If you try your website on smaller screens, you will notice that it overflows, for better responsiveness, you can:

    1 - use the rem unit instead of px.

    Each rem equals 16px by default, to avoid impossible rem to px calculations, you can set the font-size of your <html> element to 62.5% which is the result of 10[px] * 1[rem] / 16[px], this will make each rem equal to 10px.

    2 - use media queries

    Good luck!

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