Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

QR-code component

mdohr07•70
@mdohr07
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 most proud of having put a little extra challenge to myself with the JavaScript instead of just enjoying my comfort zone.

I'd do differently next time...I'd like to say I'd linger less in trying to perfect stuff and finish faster instead, but that would be just lying to myself :p

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

The JavaScript part that I brought upon myself was a bit challenging. My solution was using ChatGPT (yes) as my tutor: I write them how I think the function should work and what I need for it and I write as much of the code as I can come up with myself. Then I have ChatGPT correct me and I ask for explanations on every part I don't understand.

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

Like what I could have done better in general but especially regarding the JavaScript or aspects of accessibility.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • bloo2kk•50
    @bloo2kk
    Posted about 1 month ago

    I really like your idea of enhancing the project by adding JavaScript — it looks very good and adds a nice dynamic touch!

  • Kadhir•90
    @kadhirshankar
    Posted about 1 month ago

    I like how you added JavaScript and made it your own. It looks clean.

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.

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