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

https://github.com/Papi84/Interactive-Pro/blob/main/style.css

Papi•280
@Papi84
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'm most proud of successfully implementing the interactive components of the project and improving my understanding of HTML, CSS, and JavaScript. It was a great learning experience to see how user interactions can be enhanced to create a more engaging interface. Next time, I would focus on refining my JavaScript skills further to optimize the code for better performance and perhaps explore more advanced JavaScript features. Additionally, I would aim to improve the responsiveness of the design across different devices and screen sizes to ensure a more seamless user experience.

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

One of the main challenges I faced was working with JavaScript to handle the interactive elements. At times, it was difficult to ensure the functionality worked as intended across different browsers. I overcame this by researching best practices for cross-browser compatibility and debugging JavaScript code more effectively. Another challenge was making sure the design was fully responsive on all screen sizes. To address this, I revisited my CSS and utilized media queries to ensure a smoother, more responsive layout. It was a learning curve, but tackling these issues helped me grow and sharpen my problem-solving skills.

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

I would appreciate feedback on optimizing my JavaScript code for better efficiency and readability. Additionally, I'd like guidance on improving the responsiveness of the design, particularly with more complex layouts on different screen sizes. Any tips on best practices for structuring CSS and handling potential performance issues would also be helpful as I continue to refine my skills in these areas.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Papi's solution.

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.