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

rating preview

NayyabAqib•650
@nayyabaqib
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 am proud that I successfully completed this project using only HTML and CSS. It was a great experience that helped me improve my front-end development skills. If I were to do this project again, I would add JavaScript to make the component more interactive and enhance the user experience.

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

i faced some challenges with CSS positioning and properly aligning the elements. Responsive design and button interactions were also a bit tricky. To overcome these challenges, I studied documentation, watched online tutorials, and used CSS Flexbox and Grid to fix the alignment issues.

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

Through this project, I learned how to design interactive UI elements and gained a better understanding of advanced CSS concepts like Flexbox and Grid. Additionally, I realized the importance of proper spacing and alignment for a good user experience. In the future, I plan to integrate JavaScript to add more interactive features.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Daniel Ayeni•1,240
    @Dannimations
    Posted 5 months ago

    It looks like you've got a good handle on CSS. That's very good. What u need to do now is add the Java-script to add functionality.

    What I'd suggest is making the user's choice into a variable, let var userInput

    then implementing that variable in a p element in the html that changes with regard to the change in the user's choice, so that when the user clicks on something, it changes the userInput.

    You can always achieve this using event listeners

    Remember that you'll also need to get the id's of each of the buttons, and then call them in the JS file

    const buttonOne = doccument.getelementbyID('buttonOne')

    this is if the button one has an id of 'buttonOne'. You can do that for the rest of the buttons. Then add an event listener:

    buttonOne.addeventlistener('click', =>{ })

    and in the event listener, set the innertext of the p element to be the value of that particular button.

    I know it's a bit confusing, but a tutorial should help more :)

  • Fehmidatanzeel•570
    @Fehmidatanzeel
    Posted 5 months ago

    awesome

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub