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

html,CSS flex and js

kehinde oyafemi•190
@kennyoyaf
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have problems sometimes with the sizing of some element in different screen because some elements in things I build change shape when in different screen sizes

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Avinash Dhauni•170
    @avinashdhauni
    Posted almost 3 years ago

    Your main-container box is too wide. You can give your .main-container a width of 30% or something. Or you can give a fixed width of 330px to the .main-container. Also, I noticed you haven't changed your font. The given font in the challenge is Overpass. But congratulations on completing the challenge

    Marked as helpful
  • Ahmed Kamel•1,190
    @hmadamk
    Posted almost 3 years ago

    you should read the read me file and add the font specified to your app if you go to the link in the readme it will open google font choose the specified weights, and copy the generated link to the top of your html if you need help you can ask me

    Marked as helpful
  • Hyron•5,870
    @hyrongennike
    Posted almost 3 years ago

    HI Kehinde

    Congratulations on finishing the project.

    Just a few things I picked up when looking at the live version when you click the submit button without clicking on the numbers it doesn't show a number out of 5 on the thank you card. You can maybe use a variable to either store a default number of 1 or only show the thank page if a number is selected. Also you should indicate which number has been selected I clicked a couple of times thinking that it wasn't working you can just add a class that makes the circle orange when the number is clicked.

    Marked as helpful

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

Oops! 😬

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

Log in with GitHub