Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive Order Summary Component Code (HTML + CSS)

accessibility
Harsh Kumar Dwivedi•720
@Harsh-Kumar-Dwivedi
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am proud that I was able to build the highly closest design in comparison to the required design. From next time, I would try to complete the project in a significant lesser amount of time without compromising on the quality of the project.

What challenges did you encounter, and how did you overcome them?

Essentially, I encountered following challenges:-

1.Responsive paragraph.

2.Designing the plan portion.

3.Box-Shadow for the payment button.

4.Designing the background of the card.

I tackled these problems calmly by researching out various possible solutions, choosing the better solution, applying the solution, modifying it and then finalizing it. I used following approaches for respective problems:-

1.Padding helped out in the problem of making the paragraph responsive as per the given design across different devices.

2.Flexbox and `` element were highly useful, in designing the plan portion.

3.Setting up the box-shadow CSS property with proper values, helped in giving the payment button a bottom box-shadow.

4.Pseudo element ::before and position: fixed; were significantly helpful in designing the background.

What specific areas of your project would you like help with?

Would love to know following:-

1.What better approach could be used for designing the background?

2.Any suggestions in general or specifically regarding code optimizations, better approaches and production worthy practices.

Checkout my solution ! Feedbacks are welcome ! Stay Happy & Well ! Happy Coding ! Thanks 😀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Devon Hughes•220
    @DevonHughesCodes
    Posted about 1 year ago

    Awesome solution @Harsh-Kumar-Dwivedi

    Looks great. The only thing I noticed from your preview is that the overall container is missing a box shadow like in the design example.

    Here's an example from my own stylesheet for referrence:

    .container { background-color: white; margin: 20px; padding-bottom: 20px; border-radius: 20px; box-shadow: 0px 10px 40px rgba(34, 34, 34, 0.2); }

    Other than that, great job and keep up the good work!

    Marked as helpful
  • Victor•730
    @therealmaduanusi
    Posted about 1 year ago

    understanding the fundamental logic of flexbox, grid and positioning can go a long way. Also good work 😁

    Marked as helpful
  • Valchali•100
    @Valchali
    Posted about 1 year ago

    You did a great job here, kudos from here!!!.

  • Harsh Kumar Dwivedi•720
    @Harsh-Kumar-Dwivedi
    Posted about 1 year ago

    In Solution retrospective,

    `` refers to <div> element

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, SASS, 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

Oops! 😬

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

Log in with GitHub