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

Responsive page with CSS Flexbox and Media query

accessibility
Abdulqaweeyu•70
@ABQ4539
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • Still trying to work my way around how the max-width and min-width properties work. More help on this will be greatly appreciated.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nneoma Njoku•1,210
    @SatellitePeace
    Posted almost 3 years ago

    Hello @ABQ4539 you did a great job

    to answer your question

    • min-width = minimum width this simply tells the browser that a particular element should not be less than a certain width for example
    main{
    min-width: 200px
    }
    

    This means the main container is allowed to grow beyond 200px but it is not allowed to shrink below 200px

    • so if your screen width becomes less than 200px, your main container will either overflow or become hidden if your overflow is set to hidden
    overflow: hidden;
    
    • max-width is the opposite of min-width
    main{
    max-width: 375px
    }
    

    This means that your container will not grow more than 375px but it can shrink below 375px

    • when using max-width, make sure you also set your width to 100% so
    main{
    max-width:375px;
    width:100%;
    }
    

    This will ensure that when the screen width shrinks your content will still look good

    • I also noticed that in some cases you set your max-width to 100% like this
       .container {
            max-width: 100%;
            display: flex;
            flex-direction: row;
            justify-content: center;
            margin-bottom: 40px;
        }
    

    instead of doing this just set the width to 100% min-width can be 100% but max-width should not be 100%

    • Lastly do not use px to set font-size instead use relative units like rem this way when the user zooms in or out the structure of the site will not be distorted

    • in fact you should should relative units like rem and em more often than px

    I HOPE THIS HELPS

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