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

Responsive order summary component with semantic html and css grid

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

Solution retrospective


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

The only challenge I encountered was getting the background image to match the design. I overcame them with some trial and error

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

I would like help with semantic html, just checking to see where I can improve and any other areas I can improve on that are noticable

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • drelu•150
    @dreelu
    Posted 3 months ago

    Ok, here we go!

    1. Instead of using a <section>, it is recommended to use a <main> in section.order-summary. Do not use <section> as a generic container.

    2. Using an <h2> for the main title looks wrong. Instead, respect the hierarchy of the title and use an <h1>.

    3. In section.order-summary__plan, section.order-summary__plan-type-container and section.order-summary__plan-type, the <section> is again being used as a generic container. Instead, try using a <div>.

    4. I also saw several <span> in your code. It is not wrong to use it, but it is preferable to use it only when you want to customize a specific part of a text using css or JavaScript. Spans like span.order-summary__plan-type__name and span.order-summary__plan-type__cost should be replaced by a <p> tag, for example, while span.order-summary__plan-change could be replaced by an <a>, with an href="#" inside the tag (This makes the aesthetic and practical part of the link work, but it doesn't take you anywhere. Very useful when the focus is just on designing.)

    I only pointed out a few things, but overall, your project is very beautiful and well done, congratulations!!

    I hope I 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