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

Responsive Stats Preview Card Component with Bootstrap

accessibility, bootstrap, tailwind-css, vue, jquery
Nurul Arifin•310
@nurularifin83
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Finally I finished this challenge, as usual, I use Bootstrap to build this challenge.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlo Autor•160
    @A14313
    Posted almost 3 years ago

    Good Job! But there are a few things I want to mention. The image is smooshed when resizing the window. Try to resize to 1000px, you'll see that the image is so smooshed. Try adding some breakpoints it will solve the problem.

    Also, I noticed that when you reached 600px the image will go down. It is okay but the image itself has a border-radius. To fix that problem, remove the border-radius to the image and add the border radius to the card itself and add overflow:hidden to the card itself. It will fix the problem.

    Lastly, it is recommended that you follow the design rules like font, spacing, etc.

    You can check out my solution and try resizing it from the smallest 375px up to the biggest possible, Try noticing the image. You can check also my code to see what I mean by media queries. I hope that this helps you.

    My solution: https://www.frontendmentor.io/solutions/mobilefirst-solution-using-css-grid-and-flexbox-9ktU1M_TTC

    Please give me feedback also in my solution. Don't forget to mark this as Helpful Thank you

    Marked as helpful
  • mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

    Marked as helpful
  • faizan•2,420
    @afaiz-space
    Posted almost 3 years ago

    Hey @nurularifin83,

    • you have not given background color.
    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

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