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

Recycled Solution for Rating Card Challenge

Open World Project•80
@OpenWorldProjectOWP
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This project has a lot of research put into it as well as recycled code from codepen. Looking at the project I understood how to make the layout and with the growth from the last challenge I was able to recognize how to get everything centered correctly. However, I was completely lost when it came to how I was going to get the entire layout to change after "submitting" a rating because I am unfamiliar with JavaScript and am very new to learning its capabilities. So, I was able to find this exact challenge published on CodePen and I used it as a template of sorts. By recycling the code from CodePen I was able to see how the elements, styles, and JS functions worked together. I decided to try to change some class names, adjust CSS, and try to match changes inside of the JS script so that I could see exactly what each function was accomplishing. With that approach, I learned how to use java to display a completely different layout and how to create a form layout without creating an actual form. I learned what :focus is in CSS and how it interacts with HTML.

Overall, I looked at this project as an opportunity to use my engineering background and implement a retro-engineering technique to learn about a technology that I know very little of and I truly believe it was the most insightful approach I could take with this challenge. Now I can expand on what I've seen here and use these concepts in future challenges.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Open World Project'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.