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

Use Html and pure Css clearly handling the bem methodology :)

Sergio Pinzón•105
@sergiopin22
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What can I improve on the receptive design friends?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this. Layout seems fine but you are missing the background image, the wave image one. Perhaps you forgot to add it?

    Some suggestions would be:

    • If you inspect your website in dev tools at the bottom, you can see that your layout is being squished. This is caused by the height: 100vh on your main tag. If you set an element to have height: 100vh it might look fine to your monitor/screen, but if you scale down your browser's height, you can see the distortions. This is because using height: 100vh only occupies the current viewport's height. Removing this will be really good or you can set a max-height: 100vh instead of height: 100vh. Also on your body tag, do not set the font-size: 2vh , do not use scaling units on font-sizes unless you are using a clamp function. Use rem units
    • Good choice on using article!
    • your page lacks h1 element, you can use the h1 to wrap the order summary text instead of using h2 on it.
    • Your proceed to payment and cancel order html element is not suited. You used div which is not accessible at all. You can use either a tag or button on those two elements. If you think that the functionality links you up in another page, use a tag. If you think that clicking those element pops up a modal or some sort, use button.
    • Also you don't have to position: absolute the attribution.

    Aside from those, good job.

    Marked as helpful
  • Sergio Pinzón•105
    @sergiopin22
    Posted almost 4 years ago

    Hey really, thank you very much, what a good feedback you have given me, I really appreciate you, I hope to continue practicing I am from Colombia and I have to translate your opinion lol

    Greetings what a good level I see that you drive :)

  • Yunus Alif•150
    @yunusanr
    Posted almost 4 years ago

    I only have a little bit feedback. I think you overuse flexbox there where we can still do without flexbox. But your project looks good for me

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub