Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Result Summary Component using Tailwind CSS

tailwind-css
Ricky Reza•40
@rickyreza12
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Thank you for taking the time to check out my frontend design using Tailwind CSS.

I would love to hear your thoughts on the design, and any feedback or alternative solutions you might have for the result summary. Your input will help me improve my skills as a developer and create even better designs in the future. So please feel free to leave a comment or suggestion, and I'll be sure to take them into consideration.

Thank you again for your time and feedback!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Piyush Paliwal•40
    @piyushpaliwal
    Posted about 2 years ago

    Great work there! I was just going through your code and here are a few observations I have.

    • Used color hex codes directly inline (ex - Line 47).
      • This will make your code less maintenable, instead you can define a tailwind.config object on your script tag and add all colors there so that you can reference them back in your code. See here for details
    • While utilizing Tailwind, it is one of the best practices to have classes sorted out as recommended by the devs, see here. As of now it is difficult to find a class in your project because of the order.
    Marked as helpful
  • Sumanth Chandana•720
    @sumanth-chandana
    Posted about 2 years ago

    Hi mate!, congrats🎉 on completing the challenge. Better take care about following points.

    • You don't have to use srcset in the img tag while already using src property.
    • Always check Frontendmentor Report Generator issues after submitting the project for removing errors and warnings.
    • Use the alt (alternate text) attribute as mentioned in your Accessibility Report. alt attribute is used for Screen readers applications.
    • Why does alt attribute matter? Read here.
    • To avoid accessibility issues "All page content should be contained by landmarks" use code as :
     <body>
        <main>
            ---your code here----
        </main>
      <footer>
      </footer>
    </body>
    

    (why does <main> matter? Read here )

    • For proper centering the container(whole card) vertically and horizontally you can also use the following simple block of code use code:
    body{
        display: flex;
        align-items: center;
        justify-content: center;
        height: 100%;
    }
    or
    

    body { min-height: 100vh; display: grid; place-content: center; }

    - When we open the GitHub repository link, you will find an About Section on the right side. There, also include a live preview link of your project. It is better for someone to check your live project while interacting with code.
    
    **I hope you will find this Feedback Helpful.**
    
    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