Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Interactive rating component

tailwind-css
subodh16728•100
@subodh16728
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi community, This is the first project that I've build using JavaScript. Please share feedback if you have any. I would love to hear that and make the improvements. I want to enhance my Javascript knowledge and that's why can you please suggest which other project should I go with now? Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sameh•430
    @SamehCode
    Posted over 1 year ago

    nice my friend but why use alert or prompt it seems ugly um , dunno . but nice work anyway. how long u learn programming ? and what is your resources my friend i want to upgrade my js skills more and more

    Marked as helpful
  • Bryan Li•3,530
    @Zy8712
    Posted over 1 year ago

    Your site looks pretty good and works as expected. The only main thing I'd change is how you implemented Tailwind. I personally would've just used Tailwind CDN to import it and then just add to a separate style.css for my custom css. Alternatively, I would've just used npm to install Tailwind so that I would have the tailwind.config file.

    Besides that, I would say that if you tweaked a couple of your text sizes and font weights a bit, its pretty much one for one to the original design. Nice work 👍

    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 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