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

Simple QR Code Component using CSS Flexbox and custom color variables

P
Schindler Dumagat•340
@schindlerdumagat
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?

What I am most proud of is that I was able to use custom CSS variables for the first time just to setup my colors in location. Specifically at the top of my style element.

:root {
      --main-bg-color: #D5E1EF;
      --title-color: #1F314F;
      --desc-color: #68778D;
    }
What challenges did you encounter, and how did you overcome them?

I had a little bit of trouble on importing the font that includes only 2 font weights. When I was trying to import the font by copying the embed link tags on google fonts website. I really wanted to only include the font weights that I only need. I did some googling and you only need to specify the font weights just like this:

``

And the font weights I only need is 400 and 700.

One other thing I struggled a little is how I can center the QR code component at the middle of the page without using flex box but I ended up using flex box because it is the only one I know and I needed to set width and height of the containing element to 100vw and 100vh respectively.

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

In this html code, I am just curious if I should have used the section tag instead of the article tag to apply some semantic meaning. I wanted to know if which is better to use? Should I have used the section tag or stick with the article tag or what tag do you recommend instead?


    
    
      Improve your front-end skills by building projects
      Scan the QR code to visit Frontend Mentor and take your coding skills to the next level
    
  
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Schindler Dumagat's solution.

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.