Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Responsive order summary component html css

P
🔅 Yuliya 🐈•330
@O-Julia-O
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?

I am proud of doing readable and understandable code. I used BEM Methodology for naming block.

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

Small challenge was with margins in flexbox block_subscription. I delete them and used flex-grow.

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

Did I use BEM correctly? If no, what should I change? How about responsiveness? Does it readable for you? If no, please, share you opinion!

Any feedbacks are important! :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Walid Hawari•100
    @whawari
    Posted 11 months ago

    Hello Yuliya, Great work! I would like to comment on the structure of your HTML elements and the usage of BEM methodology.

    HTML elements structure: you do not need to add extra unnecessary divs, example:

    <div> <a class="card-subcription__button">Change</a> </div> Always think of [block and inline level elements](https://www.geeksforgeeks.org/html-block-and-inline-elements/).

    BEM methodology: You can find all your answers in this article

    Here is an updated version of the HTML file structure, try writing CSS using the new HTML structure:

    <main class="background"> <article class="card"> <img src="./images/illustration-hero.svg" alt="hero image" class="card__hero" />
        <h1 class="card__headline">Order Summary</h1>
    
        <p class="card__paragraph">
          You can now listen to millions of songs, audiobooks, and podcasts on
          any device anywhere you like!
        </p>
    
        <div class="card__subscription">
          <img
            class="card__icon"
            src="./images/icon-music.svg"
            alt="icon music"
          />
    
          <div class="card__details">
            <h2 class="card__plan">Annual Plan</h2>
            <p class="card__price">$59.99/year</p>
          </div>
    
          <a class="button button--text">Change</a>
        </div>
    
        <button class="button button--contained button--primary">
          Proceed to Payment
        </button>
    
        <button class="button button--secondary">Cancel Order</button>
      </article>
    </main>
    

    Best, Walid Hawari

    Marked as helpful
  • Amjad Shadid•810
    @amjadsh97
    Posted 11 months ago

    Hey Yuliya, Great work! I would like to comment on css.

    you can wrap .card__text, .card-wrapper__subscription and .card-footer with another element and then add padding 3rem instead of add margin(left and right) for each element.

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, SASS, 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