Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

HTML

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

Solution retrospective


What are you most proud of, and what would you do differently next time?

The challenge, makes me love coming for more challenges. Well i'll say being able to design something close to the original design means that am getting closer to being perfect. I try to be exact next time i mean with the U/I.

What challenges did you encounter, and how did you overcome them?

Actually adding the background image was a bit strange cos it's my first time of coming across it, am familiar with the normal background color, but not image , but am happy i found a way around it.

What specific areas of your project would you like help with?

I need an honest overall review.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar Dwivedi•720
    @Harsh-Kumar-Dwivedi
    Posted over 1 year ago

    Hi @Valchali ,

    Nice Solution !

    I would suggest following:-

    1.Add space and more border radius to the plan pricing section, You can prefer following:-

    .icon-music {
        padding: 15px;
        border-radius: 13px;
    }
    

    2.Prefer changing margin-left to margin-right in icon class.

    3.Try implementing active states and in that try using opacity CSS property for the required effect.

    4.Once you are done with your solution, try to go through your code in order and spot the difference, they try eliminating the difference and it loops until the required design is achieved.

    5.Feel free to ask community for suggestions, improvements and help.

    Hope these suggestions are helpful !

    Stay Happy & Healthy !

    Happy Coding !

    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