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

Interactive rating component JS

sass/scss
IO•710
@i000o
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 proud to have tackled my first JavaScript project! It wasn't easy. I've done a course on "conversant" JS so I had some notions of how to go about this task (for instance, with a if/else statement), but not with much confidence. After some research, I found my starting points and began using AI (Copilot) to assist me in tackling the problem-solving. While I didn't write my Javascript 'blindly' (as I would with CSS), I was able to gather a code block that I could understand and that got the task done. I feel initiated into using small Javascript components to achieve some interactivity on otherwise static sites.

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

The challenge was really with Javascript. I learnt about event listeners for the first time, saw callback functions in action, declared variables to use later and used some methods. AI was really helpful in being a tool to demystify the ways that I could approach this task and with small but sure steps, I made progress over time.

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

I would love some help with box-shadow for this challenge. I don't have the Figma file, so I'm guessing how it's been designed, but I really couldn't put my finger on it. Mine doesn't perfectly match the design. Can anyone show me how the code should look? You can particularly see my struggle on the thank-you state.

Secondly, please check that my Javascript makes sense and if there's anyway to simplify it, do let me know.

Thirdly, I always welcome Sass critique. I'm going for streamlined simplicity if I can. I have some comments in there of things I think could be improved, but further thoughts are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on IO's solution.

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.