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

Order summary component

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

Solution retrospective


What I have learned / practised in this project:

  • box shadow
  • the solution is sometimes not that hard (I've first set the background-picture with pseudo-elements, but it was just a simply background image...)

What was difficult?

  • I find it sometimes difficult to know what html element that i could use, for example: The price and type of the plan (annual plan/$59.99 ) I was in doubt about using a p or an ul.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 2 years ago

    Hi, I hope this feedback helps

    1. There should be some space aroubd the card at all times. This is hitting my screen edges. You could add a little margin to the component or a little padding to its wrapper
    2. This is one component, meaning it is only one chunk of meaningful content. It cannot have a header element (that is a banner landmark on a page that should sit outside of main and it's purpose if for content that repeats on every page). And it should not have a section inside. This whole card could be one section if you wanted but there is no semantic benefits to doing that
    1. not necessarily a problem but can you explain why you've chosen the interactive elements you have done for change, proceed and cancel? What do you expect to happen on click of each of these? Do you understand the key differences between anchors and buttons, and when each should be used?
    2. you don't need a paragraph inside a button (I'm not even sure that would be valid html tbh)
    3. CSS looks good to me. The only things if consider changing are the inline-margins in the plan box. Id recommend using gap there and flex-grow on the middle item. I'd also consider adding in flex wrap as a defensive style for if/when text sizes are enlarged and the content may not fit on one line'.
    4. consider setting the max width in rem instead of pixels on the component
    5. consider making the top image width 100% instead of setting explicit px width in a media query
    Marked as helpful
  • Faisal Ahmed•410
    @faisalahmed11
    Posted about 2 years ago

    @Thewatcher13, your submission is greatly appreciated, and you are right on the learning progress, that reduces the difficulty level. and finally, I would say <p> tag is the clear winner and an easy way to go in this situation.

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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