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

Order Summary Component with Vanilla HTML and CSS

tizerk•240
@tizerk
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback/thoughts are greatly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alper•1,090
    @adonmez04
    Posted over 2 years ago

    Hi @tizerk,

    I checked your code. It's a good solution, keep coding. I have some suggestions for you.

    1 - I recommended to use <a> tag for button. <button> tag uses useally as a submit a form.

    2 - Also, you can follow this order to write your <a> tag in CSS: a:link, a:visited {} and a:hover, a:active {} It's best practice.

    3 - margin: none; It'll be better margin:0. Use numeric style.

    4 -<img> tag is an inline element. It has a white line at the bottom. It'll be a problem on mobile. You can change its display property as :display: block

    5 - border-radius: 2rem 2rem 0rem 0rem; You don't need this in the img tag. You can just write this code to img tag's parent: overflow:hidden; It'll execute the same way.

    Check some good solutions and implement to your code. I hope these will help you to improve your perspective. Keep coding. All the best.

    Marked as helpful
  • Hassia Issah•50,390
    @Hassiai
    Posted over 2 years ago

    wrap <div class="attribution"> in the footer tag to fix the accessibility issue.

    You forgot to give the body a background-image with a background-size of contain and a background-repeat of no-repeat.

    In the media query, change the background-image of the body.

    For a responsive content, replace the width in .container with max-width. e.g.: max-width: 27rem which is 432px.

    To center .container on the page using flexbox, add min-height:100vh; display: flex; align-items: center: justify-content: center; to the body.

     To center .container on the page using flexbox:
    body{
    min-height: 100vh;
    display: flex;
    align-items: center;
    justify-content: center;
    }
    

    Hope am helpful.

    Well done for completing this challenge. HAPPY CODING

    Marked as helpful
  • Muhammadh•1,140
    @Mr-jaw
    Posted over 2 years ago

    Hello there 👋

    Congratulations on completing the challenge

    HTML 📄

    • replace <div class="attribution"> with the <footer> tag to fix accessibility issues.

    • Also use <em> or <small> for short text rather than using <p> which is used fro descriptive text.

    <p class="annual-header">Annual Plan</p>
    <p class="annual-price">$59.99/year</p>
    

    CSS 🎨

    • Add a max-width of 25em or something like that to decrease the size of the card to bring it closer to the original design
    .container {
           max-width: 25em;
    }
    

    I hope this was useful 😊

    HAPPY CODING

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub