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

Order Summary Component Using HTML & CSS.

Muzhda Noorzad•30
@MuzhdaN
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedback of any kind would be greatly appreciated :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muzhda Noorzad•30
    @MuzhdaN
    Posted over 3 years ago

    @Kareemah-codes There have been some minor but crucial points raised by you. I will keep your advice in mind when I work on my next project :)

    p.s Definitely, I will take a look at your projects as well.

  • Kareemah Ajina•120
    @Kareemah-codes
    Posted over 3 years ago

    Thank you!

  • Kareemah Ajina•120
    @Kareemah-codes
    Posted over 3 years ago

    Hello, so I have a few pointers if I may:

    1. Try using semantic HTML, going to your code there is just a lot of divs in places that could be semantic. For example, instead of using divs for buttons, you could just use your button tag. It offers the same functionality but is just a bit more readable. Semantic HTML is also best for accessibility purposes. You could dedicate two hours tops to learning it, it's really not that difficult.

    2. Asides from that, I think you are good to go. If I wanted to get nitpicky, I would say that the space between the "annual plan" area is too close to the "change" area. I looked through your code and it looks to me like you made a mistake in the divs. There is a div whose class is "left-part", I am guessing change is supposed to be in a div with a class "right-part" so that you can properly space them out. I may be wrong though.

    I am a beginner, kindly consider giving me feedback on the projects I have completed. I would really appreciate it.

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

Oops! 😬

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

Log in with GitHub