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

Interactive rating component solution | Responsive |

P
🔅 Yuliya 🐈•330
@O-Julia-O
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm most proud of how I was able to connect all the parts — HTML, CSS, and JavaScript — into a working and visually clean component. It was satisfying to see the "Thank you" screen update dynamically based on user input. It felt like building a real interactive app.

Next time, I would focus more on accessibility and keyboard navigation. I would also consider writing more modular JavaScript code to improve readability and reusability.

What challenges did you encounter, and how did you overcome them?

One of the challenges I faced was getting the button interaction to work correctly — when selecting a rating, only one button should be highlighted, and the others should reset. At first, the class wasn’t being applied as expected. I realized that either the JavaScript was running before the DOM had loaded, or the selector was incorrect.

I fixed this by checking the class names carefully and moving my script to the bottom of the HTML file to make sure the elements existed when the script ran. Another challenge was showing the selected rating on the thank-you screen, which I solved by saving the selection in a variable and inserting it into the DOM on submit.

What specific areas of your project would you like help with?

I’d like to get more confident with structuring JavaScript code for better readability and scalability — for example, organizing functions, separating logic, or even using modules.
I'm also curious about best practices for accessibility (a11y), especially when building interactive components like buttons and forms.

In addition, I’d love feedback on how to improve my CSS organization — maybe using BEM more consistently or learning when it's a good idea to switch to utility-first frameworks like Tailwind.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Edivandro Lima•335
    @EdivandroLima
    Posted 2 months ago

    good

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