Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 17 days ago

Interactive Rating Component – HTML, CSS & JavaScript Solution

pure-css, animation
Carlos Alberto da Silva•280
@slayer-br
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 well the layout adapts to different screen sizes and how intuitive the user interaction turned out. Next time, I’d consider using a component-based JavaScript framework like React or Vue to practice state management and modular structure.

(pt-BR) Tenho orgulho principalmente de como o layout se adapta bem a diferentes tamanhos de tela e de como a interação do usuário ficou intuitiva. Da próxima vez, eu consideraria usar um framework baseado em componentes como React ou Vue para praticar gerenciamento de estado e estrutura modular.

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

One challenge was managing the toggle between the rating and thank-you states in a clean way. I overcame it by creating utility functions to manage DOM class changes and by keeping the logic modular. I also took time to make the design pixel-perfect according to the JPGs.

(pt-BR) Um dos desafios foi gerenciar a troca entre os estados de avaliação e de agradecimento de forma limpa. Superei isso criando funções utilitárias para manipular as classes no DOM e mantendo a lógica modular. Também me dediquei a deixar o design o mais próximo possível do layout fornecido em JPG.

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

I'd love feedback on the JavaScript structure:

  • Could the DOM manipulation or event handling be optimized further?
  • Are there better practices for managing the UI state without using a framework?
  • Any accessibility issues I might have missed?

(pt-BR) Gostaria de receber feedback sobre a estrutura do JavaScript:

  • A manipulação do DOM ou o tratamento de eventos poderia ser otimizado?
  • Existem melhores práticas para gerenciar o estado da interface sem usar um framework?
  • Há algum problema de acessibilidade que eu possa ter deixado passar?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • UmairFaiser•100
    @UmairFaiser
    Posted 17 days ago

    Awesome work

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