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

Order summary using flexbox

Toyin Robinson•20
@toyrobs
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Aligning my page was one of the biggest issues I faced

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yui•50
    @yterai
    Posted about 3 years ago

    Your code looks neat and super clean! I'm gonna try that next time :)

  • maia•300
    @maiaflow
    Posted about 3 years ago

    Great work on this Toyin! It looks perfect! In your code, I like your semantic class names, I'm going to work on using those next time. Something else I want to try next time that we both didn't do is organizing your css into sections with commented out headers. Another one of those is deleting any commented out lines as a final clean up before submitting. Excited to see your next one!

  • Eric Salvi•1,350
    @ericsalvi
    Posted about 3 years ago

    Hey Toyin,

    Great job on your first submission. Checked out your code and it looks clean!

    A few things I would try to do for your next challenges is to always check out the validation for accessibility or HTML. Either do this before you submit by using axe DevTools extension or you can check out the report that FrontendMentor generates here.

    One thing I would suggest doing before you submit is to take all of your CSS and run it through a tool such as https://autoprefixer.github.io/. What it will do is generate any required additional CSS to make this submission work on all platforms and browsers. The best way to almost be fully compatible.

    For your links instead of using # for these types of components, I'd suggest using javascript:void(0) instead as this will not refresh the page when a link is clicked, unlike using #.

    Great work again and I cannot wait to see more of your work.

    Keep up that momentum!

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