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

Responsive Interactive rating component using JavaScript

bootstrap
Manuel-D-Creator•10
@Manuel-D-Creator
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 structured my code throughout the project. I focused on writing semantic HTML, organizing my CSS efficiently, and ensuring design responsiveness across different screen sizes. Additionally, I took extra care to follow best practices, which made debugging and refining the project much easier. I'm also very proud as this is my very first project involving JavaScript after learning the basics of the language. Next time, I would focus more on optimizing my workflow.

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

One of the challenges I encountered was implementing certain JavaScript functionalities. There were some operations I wasn't entirely familiar with, which made it difficult to achieve the desired functionality right away. To overcome this, I did some research on how to use the classList property to check if a particular element contains a particular class by using the ".contains" property. This experience helped me deepen my understanding of JavaScript interactivity and improved my problem-solving skills.

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

I would appreciate feedback on my JavaScript implementation, particularly on how I handled event listeners and classList. While I was able to make the functionality work, I'd like to know if there's a more efficient or cleaner way to achieve the same result. Additionally, I'd love guidance on improving my CSS organization. I feel like I might have written some redundant styles, and I want to ensure that my approach is structured and maintainable. Finally, if there are any best practices I might have missed, whether in JavaScript, HTML, or CSS, I'd love to hear any recommendations for improvement.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Manuel-D-Creator'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.