Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

First Time JS attempt

NBD•240
@bdal90
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Dear All,

Here is my first project using JavaScript which was challenging, but fun at the same time. Overall, I am not very satisfied with my CSS, it just ended up being rather messy (again) despite the fact that the outcome looks fine. Any suggestions?

Cheers,

Dalma

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tomás Pereira•510
    @TomasPereira-Dev
    Posted over 1 year ago

    Hey, what's up? I just read your code, hope this tips helps you a little.

    1)The background from the container uses a gradient instead of a solid color, that's what makes that light-gray-to-black effect, here is more information about it.

    2)You need to add a the max-width prop to the paragraph, that's what makes the brakes of line, when using it to limit text lines you need to use the ch unit, what it does is counting an amount of characters based on the space of a 0 in your font, for example 30 ch = 30 (0) characters.

    3)Avoid absolute positioning, it makes everything more hard that it should be, in this case you only need to use flexbox, notice the amount of space between the star and the paragraph, notice how it's the same between the paragraph and the numbers, you can achieve this using the gap property for flexbox, what it does is adding a even gap between every element in a container, not margin needed, you will use it a lot.

    This is all I got for now, good luck!.

    Marked as helpful
  • dnomjr•210
    @dnomjr
    Posted over 1 year ago

    Nice work!

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

Oops! 😬

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

Log in with GitHub