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

Stats Preview Card (Vanilla CSS - Custom Design + Text Animation)

Lucas 👾•104,200
@correlucas
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


👾 Hello, Frontend Mentor coding community. This is my solution for the Stats Preview Card

Last month I learned a lots stuff giving feedback and fixing my old solution. You guys don't have idea how much code I've cleaned just by deleting unnecessary divs, fixing responsivity issues cause by elements with fixed width and many other stuff like that, more I study more I realize how noob I am with CSS/HTML. But was really good to see how bad was the old solution and how I was able to fix it with the knowledge I get by giving feedback and looking the others code.

I had to update this challenge because my friend @Adriano Escarabote told that my older solution wasn't not good enough and that was not responsive on his Nokia 3310 and also in his Apple Watch. So I paid a lots of attention in order to fix the responsiveness issues and now the solution seems a little little little better. Thank you Adriano!

🎨 I've added some custom features:

  • 👨‍🎨 Custom Gradients
  • 🎨 Highlighted Text Animation
  • 👾 Gradient Overlay Effect

😎 I saw multiple solutions with the exact some custom design and animations details I've add, this doesn't bother and I don't want the credits or attribution.

😲 My advice is that instead of just copy and paste it, improve it, you can use these lines of code and improve your solution by customizing it, opening Figma and playing with your design, you'll learn a lots of stuff and possible even better results than mine, just paste and copying some lines of codes will not teach you nothing unless you try to customize it by yourself. So don't limit yourself by using a poor code and design, improve it.

❤️ For those who just copy the code/design and claimed that were an original solution, its fine, this shows that both of us have a good taste for design and like to customize out solutions.

And please, feel free to leave any feedback and help me to improve my solution!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Great work Lucas, I love the background moving gradient that you're using! I'm also doing the same thing where I'm going back to my old designs and cleaning them up, especially after seeing the different ways people wrote their solutions. Like you, I feel like I learned so much when I spend the time to review my old code and see how to improve so that I can avoid making the same mistakes again.

    I also love the advice you gave about learning from copied code. Truly great words spoken by a great mentor! 🙂

    Marked as helpful
  • Adriano•42,890
    @AdrianoEscarabote
    Posted almost 3 years ago

    That turned out great. I checked the responsiveness of the project here on my nokia 3310 and it really turned out amazing.

    I really liked the detail that stood out a lot, which in this case was the “R” you put in 'analytics' ahuauhauhau

    But seriously, you're insane, always excelling with creative layouts, I've never seen any layouts like this. Thanks for the opportunity to get some relevant reference for my next project.

    Marked as helpful
  • Okudero Michael•350
    @MicMond01
    Posted over 2 years ago

    I love the gradient

  • Yefry Sanchez•330
    @y25sanchez
    Posted almost 3 years ago

    Great job Lucas, your solutions are amazing.

  • Fuhad Raheem•100
    @FuhadRaheem
    Posted almost 3 years ago

    @Lucas this is super perfect... i love as the text color is changing

  • JO•60
    @myspace8
    Posted almost 3 years ago

    Love those custom gradients. Great work, Lucas.!

  • Johnny•490
    @johnnysedh3lllo
    Posted almost 3 years ago

    amazing job, lucas!!!!, very initiative as always.

  • Christian Patrick Nebab•1,080
    @Dng120696
    Posted about 2 years ago

    damn so nice man, how to be you bro can you teach me ? gonna appreciate it thank you

  • Adeola Ganiu•1,320
    @Deolabest
    Posted over 2 years ago

    Amazing work!

    I can't seem to find the style.css file for this project in your Github.

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub