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

first mobile-solution using CSS flexbox.

accessibility, web-components
WonteDev•20
@Promise-Wonte
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


please can someone explain responsiveness and how I can apply it on both mobile and desktop? thank you!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • BBualdo•540
    @BBualdo
    Posted almost 2 years ago

    Hi, if you want to set different styles on different screen size you have to use media queries.

    To do this you can wrap all your styles in:

    @media (max-width: 400px) {
    ***your styles***
    }
    

    It means that all of your styling will be applied until page width crosses 400px.

    So you can copy all your styles twice. One for @media (max-width: 400px) {} and one for @media (min-width: 401px) {} and then just style it for desktop. In that the changes won't be applied for Mobile View.

    And about responsiveness I have one advice: Avoid hard height and width settings of the elements unless you really have to do it. Pages are responsive by default. But if you have to do it temporarly, use max-width or min-width instead of width. Same rule for height. And try to set it with vw and vh instead of px.

    vw is ViewportWidth (100vw means it will always have width equal to page width). vh is ViewportHeight (100vh means it will always have height equal to page height).

    Good luck!

    Marked as helpful
  • Allan Nunes•490
    @Alleared
    Posted almost 2 years ago

    You need to use Media Queries for that. You use Media queries to determine how the page is going to behave in a determinate size. But you have to code every possible screen size you want to add.

    The one you've done now should be inside a media query with a width of 400px or so. You just need to code the desktop version now. Remember that the desktop version comes first in the Cascade, and the mobile version comes after.

    Marked as helpful

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