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

Order Summary Component using HTML and CSS

Miguel•70
@mogs7
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Is my code too messy? I feel that since this project is just a one pager, I felt that it was okay for my CSS references to be put however. I assume this is bad practice and would like to ask for advice on what should be done.

Is the HTML structure of my code okay? And what improvements would you suggest?

I would also like to ask if my selector references are alright. For example, in the stylesheet, I've set properties for tags like h3 and p and was wondering if doing this will mess the whole code in anyway, especially in bigger projects?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kent O'Sullivan•1,870
    @12Kentos
    Posted about 3 years ago

    Hey @mogs7,

    Nice job on completing this challenge! It's looking good. :)

    In response to your questions,

    I think your code is organized ok, but you will definitely want to start practicing now organizing your code in a way that makes sense to you, so when you come back to it months/years later it still makes sense. An easy way to organize code, is simply to add comments to it. That way you can look at the comment and easily know what the next section/sections of code are for.

    I think your html structure is fine. I didn't see any big issues with it, however I would suggest at some point looking into html naming conventions like BEM.

    I would suggest in the future you avoid selecting elements directly like you did in the following code.

    p{ color:hsl(224, 23%, 55%); font-size: 16px; }

    This will affect every single p element you have on the page, and in bigger projects this would affect a lot of your work.

    I would suggest either using a more specific selector, or better yet using a class. If you go the first route of using a more specific selector, this can lead to specificity wars, which is not a fun thing to deal with.

    Here's a really good video by Kevin Powell in which he gives some good suggestions on best practices.

    Kevin Powell Specificity

    Let me know if you have any other questions!

    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