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

Rating component [HTML/SCSS/JS] + animations

Adam•60
@Vorczu
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  1. Dont know a thing about gradient bg, I dont know is that a good option or should I do it different
  2. Rating detector - its looking simple but maybe an event listener will be a better option ?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yuliya•230
    @Ambrolla
    Posted almost 3 years ago

    Hello Adam!

    First, good job on your code and for trying! Second, I try to do my best following directions (answering your question about color gradient). So, yes, I think it is important. :) Third, there are some files in your github repo that I would include in the .gitignore. I recommend you reading about it! For example, you don't need to include style-guide :) And I'm a bit confused what is .css.map is, but I'll google it later.

    Fourth, I would suggest instead of this: <div id="1" class="number" onclick="ratCilcked(this.id)">1</div> <div id="2" class="number" onclick="ratCilcked(this.id)">2</div> <div id="3" class="number" onclick="ratCilcked(this.id)">3</div> <div id="4" class="number" onclick="ratCilcked(this.id)">4</div> <div id="5" class="number" onclick="ratCilcked(this.id)">5</div>

    Use event-target and event listener.

  • Mustafa DEDE•130
    @mustafadede
    Posted almost 3 years ago

    Hi Adam! Your button have a border but design not. You should delete your border in your css file like border: 0;

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub