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

Order Summary Component using Flexbox

Ken•935
@kenreibman
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


THIS IS MY SECOND ATTEMPT... I spent my whole weekend learning how to replicate this with zero knowledge in HTML and CSS. I tried using only Google, and no YouTube tutorials.

I am still trying to grasp media queries and how to make everything responsive.

If anyone has any suggestions on how I can write my code differently, please let me know! Any feedback out of your time is greatly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • darryncodes•6,350
    @darryncodes
    Posted almost 4 years ago

    Hi Ken,

    Great effort, really close to the design - well done!

    Some fundamentals:

    • Look into semantic html
    • Heading structure
    • A Complete Guide to Flexbox
    • A Complete Guide to Grid

    Consider using relative units instead of absolute units for responsive design. I can see you have used rem in places, you'll need to change the root font-size with media queries to see the magic happen. Here is some information to get you started:

    • css unit best practice
    • a brief guide on responsive web design

    And finally an awesome guide:

    • A Step-By-Step Process for Turning Designs Into Code

    All the best with your journey!

    Marked as helpful
  • Patryk Besler•355
    @beslerpatryk
    Posted almost 4 years ago

    Awesome job Ken! I recommend you to get more familiar with CSS display properties such as grid and flex. It will definitely help you set up the proper layout for your components. I looked up your HTML code. You should put elements in div tags only where there is a need for that. For example, putting h1 tag inside div creates unnecessary lines of code. The overall outcome looks solid. Good luck with your future projects!

    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

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