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

Responsive solution to Stats-Preview-card-component

vanilla-extract
Aryan Sethi•360
@Aryan-ki-codepanti
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


From many of such challenges there are no more than 2 breakpoints described in challenge resulting in less responsiveness of designs at tablet size though they work on mobile , laptop

Drop any suggestions or constructive criticisms

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • MikevPeeren•2,100
    @MikevPeeren
    Posted over 3 years ago

    Hey 👋

    I can't really find anything other than maybe the image overlay being of a different color. Other than that great job 👏

    Marked as helpful
  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 3 years ago

    Hey, great work on this one. Desktop layout looks great, just the overlay is bit too bright. Resizing the screen creates issues on the site. If you go to like 550px, you will notice that the image on the right side is now very small and just looking at 470px upwards, the image is not being resized or doesn't scale that well. Though the mobile state looks fine.

    Some suggestions on the site would be:

    • Change the header into using main tag since a primary header usually contains the topmost part of the site which includes the website-logo, the navlinks and some other controls. But for this, there are none and this whole layout is the main-content of the site itself.
    • br on the h1 is not needed since it will automatically wrapped the text on another row since the container will limit the h1 size.
    • You could used ul for the .lower selector since those are list of items that are inside it.
    • When wrapping up a text-content, make sure that it is inside a meaningful element like p tag or heading tag and not using like div, span to wrap the text. Use p tag on the texts like companies and other.
    • Add an extra aria-hidden="true" on the image so that it won't be picked up by other screen-reader. Though on this one, I find the image meaningful and I would add a descriptive alt on it.
    • Remove the position: absolute on the footer tag since it just gets on the screen when using dev tools at the bottom.
    • Lastly, addressing the issue about the responsiveness especially for the image.

    Aside from those, great job again on this one.

    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