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

QR Code Component

Muhammad Farhan Rosidi•70
@MuhammadFarhanRosidi
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mario J.•30
    @mjohnson0923
    Posted 7 months ago

    Your solution looks great!

    The only suggestion I would make would be to create a separate CSS style sheet to cut down on the code in the HTML file. You can reference the style sheet in the 'head' section and style have it styled the way that you have now.

    Keep up the great work!

    Marked as helpful
  • Tara Desk•360
    @TaraDesk
    Posted 6 months ago

    Hey, great job on completing the QR Code challenge! 😊

    You've done a great job with the card layout and the clean use of flexbox for centering elements—well done

    One thing that might help is adding media queries so the card looks better on smaller screens. Right now, it has a fixed size, which could make it a bit squished on mobile. Just tweaking the width and padding would make it way more responsive.

    Also, maybe think about using more semantic tags like <main> or <section>. It makes the code cleaner and helps with accessibility too.

    But honestly, great job—keep it up and happy coding! 😊

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub