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

Purely HTML and CSS

Adaeze Ikemefuna•95
@AdaezeIkemefuna
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This simple work, to my surprise, took me several hours to complete and honestly speaking, most of it was achieved through trial-and-error method.

I'm just starting out and I'm a bit proud but I NEED HELP and suggestions so next time, i can build a simple task in record time and with lesser code.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anmol Kapil•655
    @anmolkapil
    Posted almost 4 years ago

    It looks good. Just fix your button width and text alignment as suggested by Ahmed Faisal

    Marked as helpful
  • Hafizan Adli•1,190
    @hafizanadli
    Posted almost 4 years ago

    Hi there, Congratulation for completing your first challenge!

    Here are a few things, I'd like to suggest,

    • if you're using vs code editor, you could do the code formatting with option+shift+F (if you're mac user) or alt+shift+F (for windows). It would be more easier to read the code
    • the annual plan part seems a bit different from design. according to your code, I suggest that you wrap the icon and text(annual plan and price) with one div. So there will be 2 div inside "price-container" instead of 3.
    • to make the component in the middle of screen. translate -50% to top and to left. or instead of using absolute position, you can use flexbox
    • for button you can set width to 100% and when hover the payment button, you can set the opacity instead of set color to purple

    Hope these could be helpful

    Keep up the great work!

    Marked as helpful
  • Ahmed Faisal•5,095
    @afrussel
    Posted almost 4 years ago
    • overall output is good. There is text alignment issue. Use text align left on annual plan text
    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