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

QR Code using HTML and CSS

Patrick•10
@pmahon628
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 am happy I completed it and it looks pretty much like the image, I know there is much more to learn and I hope to have better code and writeups as time goes on.

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

I started off by trying to do too much but in the end I simplified the code and kept it simple and that served me a lot better

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

I am pretty happy with how it turned out, I know I can fine tune some things and get better, this is my first submission and I look forward to many more

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eric Salvi•1,350
    @ericsalvi
    Posted 9 months ago

    Congrats on your first submission!!!

    First here are some suggestions. I think you are missing some CSS for the image. I would try adding width: 100% height: auto and set border-radius: 10px. This should get your image looking close to the original and to not spill out beyond its container.

    I don’t think your font is loading as I am seeing just the default system sans-serif load. I am not seeing the Google import or linked code in the Head of your HTML.

    Something I challenged myself on is to keep your code as semantic as possible. Great for accessibility purposes. I would try to avoid any div or span tags. With this one you could have turned the div tag with a class name of card into a more semantic article tag. Running this through AxeDevTools (great Chrome extension to add to your toolkit) shows 3 accessibility issues. One way to overcome this is to convert your HTML div into an article tag and then wrap this article tag with a main tag. 



    You also do not have an ALT tag on your image.

    Lastly, I do notice some slight differences between the font colors and alignment. It is very important to try and get the completed work matching as close as possible. This will really start training your eyes to these little details.

    Again, great job on your submission and I am looking forward to seeing more that you do!

    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