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

Responsive Card Component with React and TailwindCSS

react, tailwind-css
James•130
@jte0711
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I added the correct font-family and font-weight, but it doesn't seem to look like the one from the Figma file, do you know what I'm doing wrong?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi James, it looks like you're using Next.js here, and so the link for the font family should go in the Head component in the Document (_document.js) file. I tried looking for it in your repo but couldn't see it; I did see you adding the web font link in your global styles, but that might not work here. I remember @KostasKv built this challenge also using Next.js and Tailwind; you can have a look at that here: https://www.frontendmentor.io/solutions/interactive-rating-tailwind-css-nextjs-first-time-trying-it-lFKFAcH4lh

    About your solution for this challenge, it looks fine to me, and the only suggestion I have is to see whether you can add in some logic for handling what happens when no rating gets selected but the user hits submit anyway.

    By the way, it looks like you are using your repo for multiple FEM projects in Next.js. That might be OK since I also use one repo for all my FEM projects, except it's mostly in plain JS and no frameworks or libraries. The only thing I'm not sure about for you is when each project needs a different font family, and I wonder if that means you'd have to paste a bunch of web font links in your Document file. I looked at your Product Preview challenge, and it doesn't look like the Fraunces and Montserrat fonts there got used either. Anyway, I hope you get this sorted, so good luck!

    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