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

interactive rating component using JavaScript

Hale•330
@halelite
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


any tips on how to write my code more efficiently would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yefree Valdez•940
    @yefreescoding
    Posted almost 2 years ago

    After checking out your solution, I have to say it looks pretty good. Everything works as expected, and the design is almost identical to the original. Just a couple of tips to make your code more semantic, accessible, and better structured.

    • <div> tags are super useful, but you should only use them in very specific situations. There are semantic tags that would make your code more readable and accessible. A good practice would be changing:
    <div class="rating-section content-container">
    

    for a:

    <main class="rating-section content-container"></main>
    
    • Other case where you should change <div> tags in your code will be this one:
    <div class="buttons">
    <div id="1" class="btn">1</div>
    <div id="2" class="btn">2</div>
    <div id="3" class="btn">3</div>
    <div id="4" class="btn">4</div>
    <div id="5" class="btn">5</div>
    </div>
    <button type="submit">Submit</button>
    
    • Notice that this component, at first glance, isn't very clear about what it is meant to do. There's a <div> container and five more <div> elements inside of it, which does not make too much sense. A good way to make this component more semantic, accessible, and well-structured is like this:
    <form id="form" class="buttons_container">
    <div class="btn">
    <input type="radio" value="1" name="oneStar" class="radio_input" checked>1</input>
    <label for="oneStar">Huey</label>
    </div>
    <div class="btn">
    <input type="radio" value="2" name="twoStar" class="radio_input">1</input>
    <label for="oneStar">Huey</label>
    </div>
    <div class="btn">
    <input type="radio" value="3" name="threeStar" class="radio_input">1</input>
    <label for="oneStar">Huey</label>
    </div>
    <div class="btn">
    <input type="radio" value="4" name="fourStar" class="radio_input">1</input>
    <label for="oneStar">Huey</label>
    </div>
    <div class="btn">
    <input type="radio" value="5" name="fiveStar" class="radio_input">1</input>
    <label for="oneStar">Huey</label>
    </div>
    <button type="submit">Submit</button>
    </div>
    
    

    Of course, this will require you to do some tweaks to your JavaScript and CSS to make it work and look good. But these are just some examples of how you should approach this type of challenge.

    Overall, you're going in the right direction. Keep it up!

    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

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