Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

create page using html, css and javascript

Praveen Singh Mahra•340
@PraveenMahra
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pranjali Sargar•520
    @Psargar616
    Posted over 1 year ago

    Hey @PraveenMahra, awesome job on the Interactive Rating Component Challenge! 🌟

    I hope you're doing well and enjoying your Frontend Mentor journey. I just had to drop you a message to say that your solution for the "Interactive Rating Component" challenge is absolutely fantastic! 🚀

    Here's what I loved:

    Stunning Visuals: Your design implementation is top-notch. The color scheme and typography choices are spot on.

    Interactivity: The way you've made the rating component interactive is a great touch. It's engaging and user-friendly.

    Responsive Design: I noticed your solution adapts smoothly to different screen sizes. Excellent job on that front!

    A couple of minor suggestions:

    Code Comments: Consider adding a few comments to explain your thought process in the code. It's incredibly helpful for anyone reviewing your work and makes it easier for you to revisit your code later.

    Accessibility: Just double-check for accessibility features to make sure your solution is usable by everyone, including those who may rely on assistive technologies.

    I have a small suggestion for you: Why not consider building a similar project using React.js in the future? Given your talent, I believe you could create something truly amazing with React's powerful features. It could be a fun challenge and a great opportunity to expand your skill set.

    Keep up the excellent work! If you decide to dive into the React version of this project or if you have any questions along the way, feel free to reach out. I'm sure you'll do brilliantly!

    Your work is already fantastic, and these suggestions are just about making it even better. Keep up the awesome work, and don't hesitate to ask if you need more feedback or have any questions.

    Cheers to your coding journey!

    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
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