Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Order Summary Component With Only HTML and CSS

opdevs•10
@opplayz
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, I'm new to HTML and CSS. I know that my code isn't practical. If you can, please give me some suggestions on how I can clean up my code. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nguyen Duy•245
    @koalalikecode
    Posted almost 4 years ago

    Congrats on finishing your challenge. It looks good for a beginner.

    However, you can improve your code by taking some steps:

    • Firstly, Instead of using a center tag <center>, you had better use a main tag like this `<main>your codes</main>
    • Secondly, you should use CSS for regulating the value of images' width and height <img class="musicicon" src="assets/icon-music.svg" alt="Music Icon" width="50%" height="50%">
    • Moreover, use your CSS to make margin, it will make your Html code clearer.<br> </br>
    • Finally, it will look better if you use an external CSS file instead of the internal one

    Aside from that, great work!

  • Obuhri•165
    @obaryo
    Posted almost 4 years ago

    for the html issues, you should remove the styling of width, height and <center> and do it in your separate css file so that it's easier to style it. For the accessibility issue, it said that you should add a main class on your body, and you can change the <div class="attribution"> to <footer class="attribution"> to remove the accessibility issue.

  • DOMINGOS JOSÉ GONÇALVES NETO•0
    @edvanio1888
    Posted almost 4 years ago

    I don't understand you, be clearer.

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

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