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

PURE HTML AND CSS

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

Solution retrospective


Can i make it better? please review it, it would be helpful!! Thanks :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • hardy•3,640
    @hardy333
    Posted almost 4 years ago

    Hey I have few suggestions:

    • add background color after background-image: declaration.
    • use more padding on button.
    • do not use bold font on everything.
    Marked as helpful
  • faiyaz rahman•260
    @faiyaz-rahman13
    Posted almost 4 years ago

    hey, everything is nice. do some more practice and improve these things. try to improve the font size, make the font bold. and to make your background make like the challenge picture. make the background on the body tag. set the background picture in CSS. set it as background-img=url(../images/background.....) then set the background as no-repeat, set the background-position on top, and adjust the height and width of the background. make the background as height:100vh. do those and I hope it will help you a lot. thank you.

    Marked as helpful
  • Lamar•515
    @Everezze
    Posted almost 4 years ago

    Hi, You need to change the font-size it's too big, and some elements are also bold like title, the button. Instead of setting the card for different width you could set a max-width so for the desktop it will never be longer than that. The annual plan section have a grayish background that you need to set. The transition time on your button might be too long but I'm not sure about this one.

    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

Oops! 😬

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

Log in with GitHub