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

Interactive rating component (Flexbox, SASS, pure JS)

Iva•120
@Ivuska
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello! This was quite challenging for me especially because of the used JS. I struggle a little bit with the syntax. I also found out that I was not completely sure what exactly I need to ask/search in google or in the forums (how to call it when I need to sent the chosen number to the next card as the selected rating).

  • do you have any tip for quite good JS tutorials, please?

I also struggled with creating the 'perfect' circle when the text is in it. I used these five properties (height; width; line-height; text-align; border-radius) to define it:

  • but I am not sure how "elegant" this solution is? Do anyone have some tips for better/easier or more used solution?

Thanks a lot in advance for anny feedback and/or help and have nice coding time!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chris Mulvany•120
    @ChrisMulvanyGH
    Posted over 3 years ago

    Hi Iva,

    Good work on this one, I don't know if you are experienced or new to frontend as your solution looks solid. So from a frontend point of view well done. The great thing about these challenges is that you can always return and refactor the CSS, HTML or JavaScript. As you learn and develop new skills you can revisit your solutions to see how your code can be more 'Elegant'. My advice "Fail a lot, and do it again, and again" this is how to become a great frontend developer.

    With regard to JavaScript coding I would highly recommend the Coursera JavaScript for Beginners Specialization. There are 4 courses in the specialization and you should be able to do all by choosing 'Audit' for free. You won't get certification when auditing but the training is really good for a beginner.

    Hope this helps!

    Chris Mulvany

    Marked as helpful

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

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