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

HTML and CSS

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

Solution retrospective


I have majorly used the POSITION attribute for positioning various text elements. Please tell whether it is the most correct way or I can use FLOAT or ALIGNMENT for positioning.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dušan Lukić•1,660
    @dusanlukic404
    Posted almost 4 years ago

    Hey Harsh, congrats on completing this challenge. I have some suggestions for you:

    • You should use proper font-family.
    • Make the card smaller and set the background size: contain on body background image.
    • Your attribution should be outside the card.
    • I suggest you to use flex or grid layout instead of positioning everything perfectly.
    • It is not responsive so make sure to change it.
    Marked as helpful
  • Jannie Hansen•110
    @Jawha3
    Posted almost 4 years ago

    Hello harshag3036, I was actually about to start this challenge myself. I think I will be using some CSS grid or flexbox to acheive the card layout. I am far from being an expert on the subject and cannot really comment on what is best practice in this scenario - that said, I do think you could have saved yourself a headache with the positioning had you used grid or flexbox.

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