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

Order summary component

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

Solution retrospective


Hello,

could you please advice on:

  1. In the part with plan and price I could not access the Change to move it to the end when used space-between and wanted to move change to the end using nth-child
  2. How can I improve working with width and height on different screens please?

Thank you in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • TayAki79•160
    @TayAki79
    Posted over 2 years ago

    Hi @Swing95, congratulations on this challenge first.

    1. I see that you use display flex on class="plan" which is a beautiful thing thus you can align all the three elements (music-icon, plan-price and change) in one line. Unfortunately the justify-content doesn't really work since you don't want the gaps between those items having the same distance. So to me I guess the way you did it with margins is the easiest way to accomplish it. Another way is to use 'display: grid'. If you are familiar with this property it would be a beautiful thing to do to get a clean code.

    2. OK, now I did view your code =). I think the best way to understand width and height is to first understand, that the size of an element is relative to the size of the body and the size of the body is relative to the size of the html page. Since the html element is the parent of everything that comes next you can say that the html width and size will take up the whole screen. Now, if you set the body's width to a 100% this means that the body width take up the same size of the html width. Which means if you resize the width of your screen smaller or bigger the body's width will follow as well. The size of the html takes up the whole screen size which is 100vh (viewport-height). Here you can also use 100vh for your body element since the project only takes up 100vh or less. If you're not quite sure about the height I would recommend to use min-height of 100vh for the body element which means that your site takes up 100vh or more than this if you have i.e. more pages the user can scroll down.

    Alright! I hope this will take you any further and if not I'd love to work and learn together with you if you want to. Just hit me up!

    Best regards,

    AkraDEV

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub