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

Order summary

Dean Hudek•290
@deksa89
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


It's my 3th challenge and I am still a newbie. What is the best practice when dealing with multiple elements side by side (such as where Annual Plan, music icon, price and change are)??? Should we use position-relative to set them up or is there a better practice? I have feeling that I am missing something on that matter.

Any feedback is welcome.

Thank you! :D

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Wisdom•80
    @Abasiekong
    Posted about 3 years ago

    First, you need to understand the visual layout of how elements are placed.

    In this case, I would suggest wrapping the Annual plan text and Pricing in a parent element:

    <div class="pricing-plan">
         <p class="pricing-plan--heading">Annual Plan</p>
         <p class="pricing-plan--sub-heading">$59.99/year</p>
    </div> 
    

    When you're done you then wrap the the Music Icon, Pricing Plan & Change button, make them share the same parent element, like this:

    <div class="summary-order-pricing">
              <img src="images/icon-music.svg" alt="Music Icon">
    
              <div class="pricing-plan">
                   <p class="pricing-plan--heading">Annual Plan</p>
                   <p class="pricing-plan--sub-heading">$59.99/year</p>
              </div> 
    
              <a href="#" class="btn-change">Change</a>
    </div>
    

    From this point, you could set the display property of the summary-order-pricing block to display as a flex container:

    .summary-order-pricing {
        display: flex;
    }
    

    and you're all set!

    Marked as helpful
  • Dean Hudek•290
    @deksa89
    Posted about 3 years ago

    Awesome @Abasiekong thank you! I appreciate it! :D

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

Oops! 😬

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

Log in with GitHub