Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 6 months ago

interactive-rating-component

react, vite
vardhanf•90
@vardhanf
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 find it difficult to deploy this React project using vite and githubpages, and resolving the image not showing case but finally i did by myself by taking more time. but finally i completed my first challenge using react

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

i find it difficult to deploy this React project using vite and githubpages, and resolving the image not showing case but finally i did by myself by taking more time , using chatgpt i ovecomed by installing

To deploy react project using vite: npm install gh-pages --save-dev; adding base in vite, scripts in package.json; npm run build, npm run deploy.

after deploying i cant see images changed some url sources and ten finally resolved

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

i would like to prefer any best are good practices in styling for now mostly, i added styles in index.css u can see once.

And i am feeling difficulty while adding colors unable too choose correctly.

if u care and help me thank u for it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • uzainmalik123•260
    @uzainmalik123
    Posted 6 months ago

    its pretty good just adjust the padding and idk why you have set a margin of 20px and auto to the card you didn't need to do that its already centered and i would say that use margin as a last option first try something else and the color are given to you in the style guide file use those you have messed up the grey color its too light.

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