Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Order summary mobile first with html and css

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

Solution retrospective


In all honesty, I am kinda disappointed that this challenge was like 5 times harder for me that it actually looks like, i feel like i should've done it way faster and way better. Im looking for literally any kind of advice at both html and css so i can get better and keep going at my front-end adventure. Thanks in advance.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rachael•610
    @RMK-creative
    Posted over 3 years ago

    Hi Bernard, nice work! Your solution looks really similar to the design

    Along with the comment already posted, I would just add to check out the responsiveness - it looks good on desktop and mobile, but tablet needs a bit of adjusting.

    What were the things that you found most challenging? I also struggle with expectation vs. reality with a lot of challenges, but I try not to focus too much on that aspect. Identifying the harder bits so I can learn from them has become much more important.

    Don't be too hard on yourself, you're doing a really awesome job!

    Marked as helpful
  • lisoviy•60
    @lisov1y
    Posted over 3 years ago

    Hey pal, you did a great job! It looks perfect to me, I just see there two things that you can fix easily:

    1. Annual plan (your accent class) is not centered in your plan box.
    2. You don't have the shadow below the payment button.

    Everything else looks great, we all struggle with this in the beginning, believe me! But don't give up and practice more, that's the only advice and you will be the best!

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
Frontend Mentor logo

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