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

Responsive Order Component with CSS Flexbox and Grid

ajensley•10
@amber-jenae-ensley
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 first submitted solution! All feedback is greatly welcome. Does anyone have a good tip or strategy for knowing what to use for your sizing units and when? With the Figma file I was able to know exactly what some heights and widths should be, but for responsiveness, should everything be relative only (like rem, em, percentages, and vw/vh)? Or are using pixels, especially for font sizes, usually okay? Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ken•4,915
    @kens-visuals
    Posted over 3 years ago

    Hey @amberensley 👋🏻

    I have some feedback for the project.

    • For the music icon, add aria-hidden="true”, because it's for decoration. You can read more about aria-hidden here.
    • Hero image should have a display: block;, it removes the line underneath the image. If you want to know what's causing it, check out the 3rd section of this video
    • Also, I suggest adding transition: all 0.2s; to the button and the links, this will make :hover smoother.
    • I won't go into many details about resetting CSS, but I'll leave this cool article here, which will make more sense than my brief explanation.
    • Lastly, let's bring the card to the center of the screen, just add min-height: 100vh to the body, and you're good to go.

    I hope this was helpful 👨🏻‍💻 to answer to your question, I'd say in my opinion it's good to use relative units for the most of the stuff, because fixed units are not good if you're trying to build a responsive website or even a small component. Other than that, you did a great job with your first project, well done. Cheers 👾

    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, SASS, 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