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

Stats Preview Card Component

Joseph•150
@joexyjay
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luis paz•390
    @Pazispeace
    Posted about 3 years ago

    Hi there Joseph! Nice solution :D I have some tips and adjustments that might help!

    • In your overlay div which is inside the images-section div. I would recommend you to apply a border-radius with the value of inherit to it (the overlay). If you look carefully the border bottom right and border top right are not rounded, that is because border-radius is not an inheritable property. For that you have to specify it in the class:
    .overlay {
        height: 100%;
        background-color: hsl(278, 75%, 33%);
        opacity: 0.5;
        border-radius: inherit; //here!!!!!
    }
    
    • I think 1500px for your image is way too much hehe, try it with 900 px or les (or a bit more) instead:
    @media (min-width: 800px)
    .images-section {
        background-image: url(images/image-header-desktop.jpg);
        width: 900px; //here!!!!!
        background-size: cover;
        background-position: initial;
        height: auto;
        border-top-left-radius: 0;
        border-bottom-right-radius: 10px;}
    
    • When shrinking the viewport, your text-section div overflows, that is because of the padding you added to it (top and bottom). Instead you can try adding display:flex with its flex direction in column, and justify-content:center; (this defines the alignment along the main axis. The main axis is Y (vertical) in this case because the flex direction is column). Additionally I added the flex-basis property this defines the default size of an element before the remaining space is distributed... Worth knowing that Flex-basis matches width when the container has flex-direction: row and a defined value other than auto. If the container had flex-direction: column, flex basis would match the height of the component, as long as its value is not auto.

    If the container has flex-direction: row, the value of the flex-basis property overrides the width property. The same with flex-direction column overriding the height property

    @media (min-width: 800px)
    .text-section {
        font-size: 20px;
        display: flex; //here!!!!!
        padding: 0 35px;
        flex-direction: column;  //here!!!!!
        justify-content: center;  //here!!!!!
        flex-basis: 80%;  //here!!!!!
    }
    

    -Try to not use px units since absolute units ( px , in , mm , cm , pt , and pc ) are as bad for accessibility and responsive design as using tables for layout

    Articles I think might be helpful:

    A complete guide to css Flexbox

    CSS Units For a Responsive Design

    PX, EM, or REM? Examining Media Query Units in 2021

    Happy Coding, I wish you a happy day! : )

    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

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