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

QR code Component

mohammedreddah•50
@mohammedreddah
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

Hello everyone !!

Thankfully i didn't face a serious issue Durring the completion of the project .

But the way i specified the font family is kinda unprofessional, because the style-guide file already gave me an url of a font family but for a reason it doesn't apply.... so i forced a similar font using the font-family property. If anyone can help with this small issue i'll be grateful : ) .

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vinny_A•50
    @Eye0001
    Posted about 1 year ago

    Hello @mohammedreddah

    Congrats on completing the challenge. You did a great job.

    For your concerns regarding the font, there are two main ways I would do it:

    1. Link/import: The first method involves going to fonts.google.com and searching for the font that fits your needs. You can then click the Get Font button in the upper right corner and then the Get embed code button. Make sure you have selected the Web option, you can then choose what font weight you want. You can either choose to use a link tag in your HTML or @import in your CSS.

    2. The second method involves you downloading the font directly to your project. Once you have done this you can use @font-face in your CSS file to use the font. The second part of this video explains it well.

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

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