Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 20 days ago

QR Component Challenge Solution

pure-css
Sneha Sikder•110
@Snehasikder
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 proud of the fact that I was able to pull it off in a few hours writing without any help or tutorial.

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

I guess the sizing was a bit problematic but after constantly trying I was able to achieve what I wanted and the result is better than I thought.

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

This looks best when browser is at 100% zoom but how to maintain the same look, is it possible? Any suggestions and a review would be appreciated.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,020
    @thisisharsh7
    Posted 20 days ago

    Great work on completing the challenge! 👏 It's impressive that you built this without external help or tutorials — that's a strong way to sharpen your skills.

    ✅ What you did well:

    • Clean use of flexbox for centering elements.
    • Proper use of semantic tags (main, footer).

    🔧 Some suggestion:

    1. Responsiveness: The .b card has a fixed width of 20% which may look too narrow on larger screens and may not adapt well on smaller devices. Consider using max-width (e.g., max-width: 320px) with width: 100% for better responsiveness.
    2. Spacing: Remove hardcoded margin-top: 200px and margin-bottom: 220px inside .b — use padding or gap inside flex container or media queries instead.
    3. Zoom Handling: To maintain consistent scaling across zoom levels, rely more on em, rem, vw/vh, and flexbox/grid units instead of hardcoded pixel values.
    4. Text: Use heading tags (h1, h2) meaningfully for accessibility and SEO. Avoid align="center" — prefer text-align: center; in CSS.

    Keep it up - happy coding!

    Marked as helpful
  • Marcos Sobral•10
    @Marcos-Sobral
    Posted 20 days ago

    It was fun to make this page because I did it without AI or searching the internet, and it's been a while since I've programmed.

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