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

HTML and CSS

accessibility, cube-css, foundation
Daniel Agofure•10
@DanielAgofure
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How can I upload fonts from google?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,870
    @AdrianoEscarabote
    Posted almost 3 years ago

    Hi Daniel Agofure, how are you?

    I really liked the result of your project, but I have some tips that I think you will like:

    A tip I give you to know how to use custom fonts in css, read this article: click here

    1- Page should contain a level-one heading click here

    2- Document should have one main landmark, you could have put all the content inside the main tag click here

    3- <html> element must have a lang attribute click here

    I noticed that the content was not centered, to fix this I did the following:

    body { display: flex; align-items: center; justify-content: center; min height: 100vh; }

    There is a file called style-guide.md in it it has all the colors and fonts that were used in the development of the project, it comes along with the images.

    the rest is great!

    Hope it helps...👍

  • kxnzx•870
    @kxnzx
    Posted almost 3 years ago

    Hello Daniel,

    The name of the font family that is required to use in this challenge is named "Outfit" in the weights Regular (400) and Bold (700).

    • Go to https://fonts.google.com/ and type in the name of the font family in the search bar
    • Click on the font family and scroll down. You will see a list with all the font weights
    • Click on the plus + to select the font weight you need, it will be added on the menu on the right side
    • You'll see two radio buttons with <link> and <import> on the right side on that menu. Select <import> and copy the following link: @import url('https://fonts.googleapis.com/css2?family=Outfit:wght@400;700&display=swap');
    • Place the this @import link inside your css file. Now you're ready to use the font family in your styles
  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Daniel, about your question regarding Google Fonts, simple click on the link in the style guide that's in the challenge zip file, and once you're in the font's Google page, click on the font weights that were listed in the style guide. After that, copy the link that's appears in the sidebar, and past that link in your head tag. You also have the option to use import in your CSS, and that is also fine. The key is to make sure you use one of these methods and that you use the appropriate one. After adding the link to your file, just use it by adding the name of the font to the appropriate selector in the CSS, like this:

    body {
      font-family: // name of font here
    }
    

    One last comment I have in looking at your code: Try not to use the huge margins to position your element The best way is just to use either flexbox or grid in the body selector.

    Great work on the whole!

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, SASS, 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