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

Interactive Rating without framework

P
DevAilurus•10
@DevAilurus
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

Rediscovering native JavaScript is a pleasure after spending six years working with JS frameworks.

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

It's possible that the naming of my classes is more suited to SCSS. Do you have specific naming conventions when you're using just plain CSS?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • tOnski86•330
    @tOnski86
    Posted 8 months ago

    This is a great question and hopefully can spark some sort of a discussion. Since you're referring to vanilla CSS, I'll come up with my two cents and hopefully the experts can weigh in on this.

    My take: Vanilla CSS Checking out your code, I see that there are a few routes you can go to. For one, you are prefixing most of your classes with .card-content. Here's how I would probably approach it.

    • Using the child combinator. Let's use both .card-content-title and .card-content-description as an example. These refer to both your H1 and p in your HTML markup. I would probably go with .card-content > H1 and .card-content > p on this, explicitly specifying that I only want styles to apply to the direct children of a .card-content div.
    • Using nesting. Although this is still not fully supported - I actually like writing styles this way. Using the same example I would probably nest my selectors like this:
    .card-content {
      &__header {
      }
      &__text{
      }
    }
    

    Modern Options Having tried a few options for my React projects - vanilla CSS, SASS, CSS Modules and recently Tailwind, I would prefer going the Tailwind route for styling. Although it uses utility classes which are directly applied to the element you are styling, I feel like being able to focus on the core logic of the application instead of having to figure out naming CSS classes has been a big advantage.

    This obviously depends on whether you are working as a web designer, where better options are available.

    Hope we get other opinions on this issue. Best of luck and keep going!

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