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

Mobile first card component using Flexbox and BEM

Gregg Christofferson•295
@gchristofferson
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Is there a better way to blend a background color with an image? I blended a linear gradient with the background image. Is there a better way I could have done this using a simple background color and background image? Maybe with the single background shorthand property?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mark Mitchell•1,820
    @markup-mitchell
    Posted over 3 years ago

    "I blended a linear gradient with the background image. Is there a better way I could have done this using a simple background color and background image?"

    That's an interesting solution! The image contrast is lower in the design, is the only slight difference I can see, and the use of a linear gradient from and to the same value looks confusing at first...

    Your solution works because gradients and images occupy the same background "space". As you suggest, background-color and background-image live in different layers so you could set:

    background-image: url('../path/to/image.jpg');
    background-color: var(--accent-color);
    

    The visual effect is the same, but IMO the code's a bit more explicit and readable.

    To reduce the contrast of the image mix-blend-mode with the exclusion or lighten values get you into the neighbourhood, although you might then need to tweak the color value for a closer visual match.

    Marked as helpful
  • P
    Ken•4,915
    @kens-visuals
    Posted over 3 years ago

    Hey @gchristofferson 👋🏻

    I just have a quick tip to help you fix the accessibility issue.

    • <div class="attribution">...</div> should be <footer class="attribution">...</footer>. These will fix the accessibility issue. Don't forget to generate a new repot after you fix it.
    • Also a bonus tip 😃 add background-color: var(--main-background); in body, so it covers the whole screen for all screen sizes.

    I hope this was helpful 👨🏻‍💻 you did a pixel perfect job, keep it up. Cheers 👾

    Marked as helpful
  • hardy•3,640
    @hardy333
    Posted over 3 years ago

    Your background needs to be full size of the body element

  • Mark Mitchell•1,820
    @markup-mitchell
    Posted over 3 years ago

    👍 you're welcome 🙂

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

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