Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 27 days ago

Interactive Rating Component using CSS Grid

Danielle Evans•100
@daniellemevans1
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 used CSS Transitions, I discovered Merge vs Rebase with Git repositories, and did a Rebase. And learned of the value attribute of an HTML button.

When changes are made to a remote Git repository, as soon as that's done, it must be pulled to the local repository. Otherwise if you make changes to the local repository you'll receive error messages and have merge discrepancies. And changes to your files must be accepted manually.

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

Making it so one page is visible and another is hidden, until the user clicks the submit button. Choosing between using radio buttons and making them look like buttons, vs using buttons and making them act like radio buttons. I chose to use buttons. I reviewed box shadow and the third parameter blur effect. I also discovered the HTML DOM element classList, the HTML DOM element getAttribute(), and reviewed null and undefined and that they are false values. The difference between hover and focus.

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

I'd like feedback on the JavaScript, as well as the HTML and the using buttons instead of radio buttons. I'd also like to be more familiar with Flexbox.

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 Danielle Evans'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

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.