Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

The simple card

Muhammad Fadll•320
@fadelun
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Thanks to everyone who visited my solution and i hope maybe someone gives some feedback or suggestion to improve my code

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fazza Razaq Amiarso•2,320
    @fazzaamiarso
    Posted over 3 years ago

    Halo Fadll! Udah mantap solusinya!

    Cuman mau kasih tips. buat const allRating = document.querySelectorAll(".radio-input"); mending ditaruh di luar sama selector yang lain di atas. Kalo di dalem function nanti dia harus terus-terusan di lakuin ulang tiap klik.

    Semoga bisa bantu ya!

  • Danilo Blas•6,300
    @Sdann26
    Posted over 3 years ago

    Hello Muhammad Fadll!

    In terms of design I think you have a good responsive design as well as the design when you switch to the other card.

    On the issue of functionality I would recommend that when clicking on submit do not leave the default value of 4, rather if the user has not chosen any of the values do not allow him to give submit.

    Also I do not recommend to use section because you are creating a component at the end that is a card that can be reused, use section when you are going to include sections in your page not necessarily in separate components because you will get a lot of those errors in the report.

    If you can add the property transiton to the elements that use pseudoclasses like :hover, :active, :focus, etc. so that at the moment of activating a state the change is not so abrupt but rather that it is seen with certain delay for example: transition: color 200ms.

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

Oops! 😬

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

Log in with GitHub