Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Solution Interactive rating component

tailwind-css
Stefan Bojkovski•720
@xStephx
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • shalri•620
    @shalri
    Posted 12 months ago

    Nice work as always! Hope this helps: pixelparallel. This extension helped improve workflow. Cheers!

  • rahimibadov•20
    @rahimibadov
    Posted 11 months ago

    I am also doing this but given colors are not suitable in the style.guide

  • Shaghisz•30
    @Shaghisz
    Posted 11 months ago

    That is a great job, but can someone actually help me with flex box glitch becuase i can't use flex inside the rate part and had to arrange them manually which led me to size and pixel error. THANK YOU!

  • Vinayak•320
    @V102002
    Posted 12 months ago

    Looks great! I am going to be starting challenges where JS has to be used so I'll start with this challenge soon. Saw your GitHub page, it looks so cool! You must have worked really hard to get to where you are! By the way, do you have advice on how to write cleaner CSS, I want to try doing it on my own before using a framework like bootstrap or tailwind later

  • chems eddine bourabia•150
    @chemsodev
    Posted 12 months ago

    cool ,can I ask you a question? with such a high level why do you keep solving newbie challenges? are you learning new things solving them? and one more question how to make a cooool loking github profile like yours?

  • ali eldien•150
    @Ali-eldien
    Posted 12 months ago

    keep up the good work. it looks pretty!

  • Rupak Mukherjee•1,370
    @hannibal1631
    Posted 12 months ago

    Looks good and works well. Great job Steph!!!

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

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