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

interactive-rating-typescript-tailwind

typescript, tailwind-css
Sreymeas Nao•210
@meass
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


your feedback will be a great help to improve my code

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Great job on completing the Interactive Rating Component project! You've successfully implemented essential web development features and styles. Here are some concise best practices recommendations to enhance your project:

    1. Separate JavaScript from HTML: Refrain from using onclick in HTML. Instead, add event listeners in your JavaScript file. This improves maintainability and separation of concerns. More on this here.

    2. Use Semantic HTML: Consider using <button> tags for interactive elements instead of <li> for ratings. This enhances accessibility. Learn more about semantic HTML here.

    3. CSS Classes for Styling: Instead of changing classes to apply styles in JavaScript, consider toggling a specific class. This approach is cleaner and more maintainable. Check out classList for more information.

    4. Accessibility Considerations: Ensure your site is accessible, especially for keyboard users and screen readers. This includes proper ARIA roles and labels. Learn about accessibility here.

    5. CSS with Tailwind: You're using Tailwind effectively. Continue exploring its utility classes for responsive design and state variants. Tailwind documentation is a great resource here.

    6. Responsive Design: Ensure your design is responsive on various devices. Media queries can help adjust layouts for different screen sizes.

    7. Feedback for User Actions: Implement visual feedback for user interactions like hover and active states on buttons for a better user experience.

    Keep up the fantastic work! Your dedication to learning and applying best practices in web development is commendable. Excited to see your growth and more intricate projects in the future!

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