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

Interactive rating component solution

PARKO001•190
@PARKO001
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 some tips to shorten the code in tailwind css

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Andrés Gutiérrez Ramírez•2,470
    @AGutierrezR
    Posted about 2 years ago

    Hello there 👋. Good job on completing the challenge!

    I have some suggestions about your code that might interest you.

    • You could organice your own base CSS using the base layer of tailwind

      @tailwind base;
      @tailwind components;
      @tailwind utilities;
      
      @layer base {
      	* {
      	    margin: 0;
      	    padding: 0;
      	    box-sizing: border-box;
      	}
      }
      

      This makes sure that this portion of code is loaded in the correct layer.

    • In order you reduce the amount of classes in tailwind you could create components with the most use clases, for example the score buttons To make a component you should added to a tailwind later in the style.css file

      @tailwind base;
      @tailwind components;
      @tailwind utilities;
      
      @layer base {
      	* {
      	    margin: 0;
      	    padding: 0;
      	    box-sizing: border-box;
      	}
      }
      
      @layer components {
      	.score-btn {
      		@apply circle h-12 w-12 bg-gray-700 flex justify-center items-center rounded-full hover:bg-gray-500 hover:text-white active:bg-orange-500 focus:bg-gray-500 focus:text-white
      	}
      }
      

      And now you should be able to use you new component in your html

      <div class="five_circles my-8 flex justify-between text-gray-400 font-semibold">
        <button class="score-btn">1</button>
        <button class="score-btn">2</button>
        <button class="score-btn">3</button>
        <button class="score-btn">4</button>
        <button class="score-btn">5</button>
      </div>
      

      Be careful not you overdo this practices, try to keep it simple, in this case, is something that you want to change and have a reaction in more element without having to change each element separately.

    Also, remember to run the build to see the final result in the screenshot

    I hope you find this helpful 😁. Most importantly, your submitted solution is fantastic!

    Happy coding!

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