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

First submission, needs work

Steven Parker•10
@stevenandrewparker
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I could not figure out how to do the purple overlay on the images. I also really struggled with the layouts, particularly of the stats.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Андрій Рогов•1,155
    @Andrii-Rohov
    Posted almost 4 years ago

    Hi there, you should try change hdref of link from /styles/style.css to ./style.css and it will aply css

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 4 years ago

    👋Hi Steven Parker! My name is Vanza!

    In my opinion, the best way to get the purple overlay is using background-blend-mode, to do that you need to do a couple things:

    • First make sure you do what Amon have said.
    • Second you can create an empty div inside the card.
    • Next, you can try to write this on your CSS:
    .card div {
      background: url('./images/image-header-mobile.jpg') no-repeat center center;
      background-color: hsl(277, 64%, 61%);
      background-blend-mode: multiply;
      background-size: cover;
    }
    

    That's it! Hopefully this solve your problem! And don't forget to add images on your GitHub repository.

    Happy Coding!

    Marked as helpful
  • Amon•2,560
    @A-amon
    Posted almost 4 years ago

    You might wanna recheck your files linking, specifically the css, favicon and images. There are no images in your repo and removing /styles/ from /styles/style.css will import the css file successfully.

    Marked as helpful
  • Malesela Kgobe•585
    @M-Kgobe
    Posted almost 4 years ago

    For the stats use a display:flex, flex-direction:column, justify-content:space-between.

    The image overlay, wrap your images in a div overlay and apply colors, object-fit border-radius.

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