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

Pixel-Perfect QR Code Component with Clean Flexbox Layout

Sandip Tamang•10
@YetiTheSleepingChancellor
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’m most proud of how clean and precise the final design turned out—matching the challenge’s layout and styling took more focus than I expected, and I nailed that attention to detail. Also, leveling up my README game with a solid, well-structured doc feels like a win for future projects.

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

Honestly, this one wasn’t super challenging since I was already comfortable with the core concepts. The main hurdle was getting the design pixel-perfect — matching spacing, font sizes, and colors took way more trial and error than coding itself. I overcame it by zooming in, double-checking specs, and tweaking CSS repeatedly until it felt just right.

Also, figuring out how to write a clear README was new territory, but using the provided template made it way easier to structure my thoughts.

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

Since this project was pretty straightforward, I’m mainly looking for feedback on subtle design details—like whether my spacing, typography, and color choices match the original challenge as closely as possible. Also, any tips on writing clearer, more professional README documentation would be super helpful.

If you spot any ways I could improve my CSS structure or overall workflow, I’m all ears!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Sandip Tamang's solution.

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.