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

qr-code

Daniel Wiśniewski•30
@TheWicha
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 don't know tbh :) Maybe i would use tailwind CSS

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

only with Figma, but i finally found out what fonts are there

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

in this project i dont know :)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Guilherme•40
    @guilhermepatriarca
    Posted over 1 year ago

    Great work :)

    These are my suggestions for improvement:

    • Use semantic HTML to replace div with article for example
    • Use alt in tag <img>
    Marked as helpful
  • Alex Blue•70
    @fake-alex-blue
    Posted over 1 year ago

    I like the approach you took to this solution. It's clear you've made some different stylistic choices, using Montserrat for the h2 text, for example - which I can't argue with personally; I think it looks good.

    The only small thing I'd mention, is that you've not added the box-shadow on the card, which is a shame; I reckon it elevates the design of the original; although to be honest it's so subtle that I completely missed it on my first attempt at the challenge.

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