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

QR code component solution

Connor McLaughlin•120
@Gingerlox
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?

One good thing I used which I just recently learned is setting width and max width on my container/wrapper div, to keep it responsive, but also keep it from stretching at wider screens widths.

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

I found this fairly simple as I have just finished a CSS course, so concepts were still pretty fresh in memory.

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

None on this, but can imagine help with be great for more complex projects.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vozmo•60
    @V0zmo
    Posted 11 months ago

    This is a fantastic code simple and easy to read for a beginner like me! Much cleaner than mine lol, responsive for any device, and also great for me to learn! If I have some feedback. Maybe add some other features of this solution, like some animation or other interesting things that involve deep knowledge of the CSS course that you learn. Other than that great job and thank you! 🥳🥳🥳

    Marked as helpful
  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 11 months ago

    Hi @Gingerlox,

    Nice project! Here are a few suggestions for improvement:

    ARIA Labels for Accessibility: Consider adding ARIA labels to enhance accessibility. This small step can make a big difference for users who rely on screen readers.

    Clickable QR Codes: While not strictly necessary, I strongly recommend always linking images on QR codes so that older users or those who might struggle with scanning can simply click on the link. This improves the user experience, particularly for those less familiar with QR codes.

    Extra Challenge - Custom QR Code: As an extra challenge, consider learning how to create your own custom QR code. It's a fun skill to have and something interesting to share with others!

    Hope these suggestions help!

    Best, Teodor

    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