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

Interactive Rating Component

Kelsey Hughes•80
@kelbri10
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


A large majority of this project was a good refresher in Vanilla JS, HTML, and CSS. One aspect I dived deeper into was how to apply widths. I realized after watching a couple videos I was depending on using 100vw in order to help with centering but learned that there were some downsides to be considered as it relates to responsiveness.

I definitely have continued questions about best practices when it comes to the units you're using (rem/em/px/vmin/vmax) and in future coding projects I want to continue to explore how to better apply that.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • HelloTechTinu•670
    @tinuola
    Posted about 2 years ago

    @Kelsey, nice solution. Good choice to use input fields to keep the logic simple.

    A minor layout tip: Set grid-template-row on the body to 1fr to position the app dead-center. Also remove margin-bottom on the wrapper class, which isn't needed.

    When it comes to units, I find myself relying more on rem by default than px, except when setting large values. Not that it makes much of a difference; but I find it spares me and anyone reading my code the mental work of figuring out that 56.25rem is equal to 900px! em is a unit I understand and like conceptually, but to me it also calls for some forethought about the effects when primary elements shift and how subsequent dependent elements (that are set with the em unit) will then behave.

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