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

React js

react
Italo Cubas Barros•40
@ItaloCubasBarros
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


While i'm doing this challenge i felt a difficulty about the divs and theirs paddings. Now i know to more pratice with positions in a web-site.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your Frontend Mentor challenge! Your project demonstrates a good understanding of React components and CSS styling. Here are a few suggestions to enhance your code:

    1. React Component Best Practices:

      • Always use self-closing tags for components without children for cleaner code. For example, change <Panel></Panel> to <Panel /> in your App.js.
      • In Panel.js, instead of a regular function, consider using arrow functions for consistency and modern syntax.
      • Example:
        const Panel = () => { /* ... */ };
        
    2. CSS Module Usage:

      • Ensure consistency in naming conventions. Your import statement uses Panel.Module.css, but the convention is usually Panel.module.css. Stick to lowercase for file names to avoid potential issues, especially on case-sensitive file systems.
    3. Improving Accessibility:

      • Add alt text to your images that describes the image. This is important for screen readers and users who might have images disabled. For decorative images, use an empty alt attribute (alt="").
      • For buttons, especially the rating buttons, consider adding aria-label to describe the action, like aria-label="Rate 1 out of 5".
      • Example:
        <img src={Star} alt="Star icon" className="Star" />
        

    Additional Resources:

    • To learn more about React best practices, check out the React official documentation.
    • For CSS modules, this CSS-Tricks guide is a great resource.
    • Explore Web Accessibility Initiative (WAI) for accessibility guidelines.

    Keep up the great work, and continue challenging yourself with new projects. Each project is a step forward in your development journey. Happy coding! 🌟💻

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