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

Rating component HTML CSS Js Mobile-flow first

accessibility, sass/scss, lighthouse
PhoenixDev22•16,830
@PhoenixDev22
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello community , I have completed another frontend mentor challenge. For sure , I've learnt few new things. I have added a pop up message using sweet alert, it appears when you submit the form and you didn't select any rating.

I would be happy , if you see something has to be improved , please don't hesitate and leave a feedback.

Thanks in advance.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Raouf•410
    @raoufrofi
    Posted almost 3 years ago

    Brother, where are you? I am noticing that you are being less active for several days
    I apologize in advance if you feel uncomfortable when I am asking you about your absence on frontend mentor...

    Someone has taken up your place on the wall of fame and I was shocked a bit

    Can you please consider telling me about it?
    I am missing You ...!

  • Cornflakes•290
    @CornflakesPlus
    Posted about 2 years ago

    Amazing design! Smooth transitions, ripple effect on click, card transition, everything as it should be.

    You coded 800 lines in CSS for such a small project. That's crazy! (In a good way :D)

    You must have like 10+ years of experience being a Web developer.

    23 likes.... JUST ? Bro, you need to change your profile pic into a cute pretty girl and pick a name like Rebecca Chambers. 300+ likes easily.

    I've seen people here swarming likes on the worst designs, just because the submission was by a pretty girl. LOL. Simps everywhere.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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