Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 27 days ago

Order Summary Card challenge Solution

bootstrap
hajarhabib•40
@hajarhabib2
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?

What I'm Most Proud Of Responsive Design: I’m proud of how the card looks great on both mobile and desktop using Bootstrap and media queries.

Clean Code: I kept the HTML and CSS organized, making it easy to maintain.

Customization: I personalized the design while staying true to the original challenge.

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

Image Border Radius Issue: I had trouble applying a border-radius to the image to make it rounded. The issue was due to the image not inheriting the parent container's properties. I solved this by ensuring the image was inside a container with overflow: hidden and applying the border radius directly to the image itself.

Flexbox Justify-content-between: The justify-content-between in Flexbox didn’t distribute the items evenly at first. I realized that the container was not properly set up, so I fixed it by ensuring all child elements were correctly aligned and adjusted the container’s properties to make sure the elements spaced out as intended.

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

Background Adjustments: I would appreciate some guidance on fine-tuning the background images for different screen sizes. While I’ve set different images for mobile and desktop, I’d like to improve the alignment and ensure they cover the screen correctly without distortion.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•6,510
    @MarziaJalili
    Posted 26 days ago

    Beautifully done! 💯

    Here's the answer from the conqueror:

    ✅ The reason the image's not shown is due to first — the wrong path provided to the url() and second — there are no quotation marks surrounding that.

    ✅ Since the CSS file is located in an outer directory, we've gotta change the path a bit:

    /* mobile */
    background-image: url("../images/pattern-background-mobile.svg");
    
    /* desktop */
    background-image: url("../images/pattern-background-mobile.svg");
    

    ✅ Also, move the line below to the initial body selector cause it's on the top in mobile too:

    position: top; 
    

    Other than that, the web looks great, keep it up!

    😎😎😎

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub