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

CSS Flexbox

bootstrap
David Adenusi•370
@Davidmide02
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How do I apply the media query in CSS to make my designs responsive?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Stephen Ikuomola•610
    @stephenikuomola
    Posted about 3 years ago
    1. You need to give your text a particular font-size.

    2. You can also check the <div class="annual"></div> and make that container to have a display:flex. Also set the annual class to be a percentage of the card as well and add margin left and right to have a margin of auto.

    3. You can also set the width of the button to be a percentage of the card and make it have a margin left and right of auto. That way the button will be responsive.

    4. I DO NOT think you need to set the <main> tag to have a width of 50% as that will make the card to shrink in width as the viewport decreases.

    I think that is all for what might be giving you problems in terms of the responsiveness.

    Happy Coding David Adenusi!!!!

  • P
    Justin Green•2,960
    @jgreen721
    Posted about 3 years ago

    Just cite this at the bottom of your CSS

    media screen and (max-width:550px){ .property1{ width: ... }; .property2{} }}

    550px is just an example. Also there is (predictably) the option of min-width as well. Make sure there is the whitespace between 'and' and the '(' as otherwise, I believe it doesn't work.

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