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

Frontendmentor News Homepage

react, vite
Wangai•410
@WangaiJM
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

The first react-vite project

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

Unable to deploy to Netlify via Github. I deployed it manually in the end.

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

I am curious, when creating @font-face, how does one use all the fonts from different folders provided by frontend mentor?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • lavollmer•410
    @lavollmer
    Posted about 1 year ago

    Hi Wangai!

    Good job on your first project!

    Getting the fonts from frontend Mentor to work was a little challenging. I first used https://transfonter.org/ to change the files into the appropriate type - WOFF and WOFF2 files. You then import those files in your assets folder - you can label them whatever you like.

    Once, that is complete, then you will have to import them into your tailwind css config file in your project like so within in the module.exports section -

    theme: { extend: { fontFamily: { 'inter-regular': ['Inter-Regular', 'sans-serif'], 'inter-bold': ['Inter Bold', 'sans-serif'], 'inter-extra-bold': ['Inter ExtraBold', 'sans-serif'], } }, },

    You will also need to import each file into your app.css file BEFORE your tailwind css utilities code within the file. This is an example of what it should look like for each font (you will need to have 3 of these - one for each font type):

    @font-face { font-family: 'Inter-Regular'; src: url('./assets/font/Inter-Regular.woff2') format('woff2'), url('./assets/font/Inter-Regular.woff') format('woff'); font-weight: 100; font-style: normal; }

    The url is the pathway to the font in your project. Change each url to match your path in your code. Hope this works! Thanks!

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub