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

Interactive Rating Component using HTML, Tailwind CSS and JavaScript

tailwind-css
Vinit Yadav•180
@vinits-repo
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey Everyone,

I just wrapped up my latest challenge, building a project using HTML, Tailwind CSS, and JavaScript. This marks my first venture into JavaScript, and I'm eager to receive feedback. Any suggestions for enhancing the solution would be greatly appreciated.

Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • subodh16728•100
    @subodh16728
    Posted over 1 year ago

    Well done 👍

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing the interactive rating component challenge from Frontend Mentor! Your commitment to building this project and making it functional is commendable. Here are some best practices and recommendations to further enhance your project:

    HTML & CSS Best Practices:

    • Semantic HTML: Great use of semantic HTML elements. Consider using <button> instead of <a> for the rating buttons, as they are more semantically correct for actions.
    • Responsive Design: Ensure your design looks good and functions well on all devices. Using relative units like em or rem instead of pixels can help enhance responsiveness.
    • CSS Organization: Your CSS is well-organized. Keep using comments and consistent formatting for better readability.
    • Use of Custom Styles: The custom style block in the HTML head is fine for small adjustments, but for larger projects, consider moving all CSS to external stylesheets.

    JavaScript Best Practices:

    • Use of const and let: Replace var with const or let for variable declarations to make your code more robust and modern.
    • Event Delegation: Consider using event delegation for handling events on the rating buttons. This approach is more efficient and scalable.
    • DRY Principle: You've done a good job following the DRY (Don't Repeat Yourself) principle. Keep this practice for maintainable and readable code.

    Accessibility:

    • Keyboard Accessibility: Ensure that all interactive elements, like your rating buttons, are accessible via keyboard navigation.
    • Screen Reader Accessibility: Use aria-label or aria-labelledby attributes to provide descriptive labels for interactive elements, which are helpful for screen reader users.

    Performance:

    • Optimize Image Loading: Check if your images can be optimized further to reduce the load time, especially for users on slower internet connections.

    Learning Resources:

    • To dive deeper into semantic HTML and accessibility, MDN Web Docs is an excellent resource.
    • For CSS best practices, CSS-Tricks offers a wealth of information.
    • To strengthen your JavaScript skills, JavaScript.info is highly recommended.

    Keep up the excellent work! Every project you build enhances your skills and brings new learning opportunities. Your progress is impressive, and by continually applying best practices, your development skills will grow even stronger. Happy coding!

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