Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

QR CODE COMPONENT

echo-script0•180
@echo-script0
A solution to the QR code component 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?

I'm most proud of successfully deploying my website and making it live using GitHub Pages. It was a great learning experience and seeing my work accessible online feels like a huge accomplishment. I also learned more about version control, hosting, and troubleshooting along the way. Next time, I’d focus on making the site even better by adding more features and refining the overall look. I’d also work on making the process smoother so I can deploy even faster without any hiccups.

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

One of the biggest challenges I faced was working with Git and GitHub. At first, pushing my code, managing branches, and handling commits felt confusing, and I ran into issues like merge conflicts and failed pushes. I had to go back and properly learn Git commands, watch tutorials, and experiment until I got comfortable with the process.

Deploying the site on GitHub Pages was another struggle. I had issues with my site not loading at first, and I wasn’t sure if my files were in the right place or if I had configured everything correctly. I troubleshooted by checking the repository settings, adjusting the file structure, and making sure my index file was correctly placed. After some trial and error (and a lot of refreshing), I finally got it to work!

Overall, these challenges helped me understand Git and GitHub much better, and now I feel way more confident deploying projects in the future.

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

I need help with selecting and implementing the correct fonts to match the design specifications. Specifically, I’d like guidance on how to properly import and apply them in my code to ensure consistency with the original design.

Additionally, I would greatly appreciate it if others could review my work and provide feedback to help improve the project

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • 👾 Ekaterine Mitagvaria 👾•7,860
    @catherineisonline
    Posted 4 months ago

    Hello, nice solution! The fonts that you need to use are always indicated in the file called style-guide.md. For this project it says that you need

    ### Font
    - Family: [Outfit](https://fonts.google.com/specimen/Outfit)
    - Weights: 400, 700
    

    There are several ways to add fonts to the project.

    👉 #1 Link the font

    As you see the project provides the link to the font you need. You can go to this link and click on the very top button Get Font. Then you will have options like getting embed code or downloading. If you click the embed code it will have all the code ready that you simply need to copy and paste. The link tag needs to be inserted in the HTML file, specifically head tag, so for you it will be

    <link rel="preconnect" href="https://fonts.googleapis.com">
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
    <link href="https://fonts.googleapis.com/css2?family=Outfit:wght@100..900&display=swap" rel="stylesheet">
    

    The part wght@100..900 is where you add the font weight, by default it includes all.

    Once done so, you simply use it in the CSS like so

    font-family: "Outfit", sans-serif;
    

    Instead, you can also try to find a font hosted on CDN. CDN will be even faster because it finds the closest server to the person using the website so this can make the process much faster.

    👉 #2 Import

    You can also import the font which can be added to the CSS file. Just make sure it's added to the very top of the file.

    @import url('https://fonts.googleapis.com/css2?family=Outfit:wght@100..900&display=swap')
    

    Then you use it the exact same way. This one is worse compared to the link because it will slow down the font parsing, so better to use the link.

    👉 #3 Downloading the font

    You can download the font and it will be even better because you don't rely on anything external but for such small projects usually it's extra hassle, at least for me. To use the downloaded fonts, you need to add them to your projects folder and then create something like this

    @font-face {
      font-family: 'Outfit';
      src: url('./fonts/Outfit.woff2') format('woff2'),
           url('./fonts/Outfit.woff') format('woff');
      font-weight: normal;
      font-style: normal;
    }
    

    You will apply this font exactly as previously

    font-family: "Outfit", sans-serif;
    

    There is also dynamic loading but it's extra at this point. In any case, give it a try! I hope it helps 🔥

    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

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