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

QR code component

tailwind-css
P
jeffgrahamcodes•260
@jeffgrahamcodes
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 organized the code turned out for this project. I paid attention to using semantic HTML and structured my CSS file thoughtfully, incorporating best practices like a CSS reset and custom properties. The final design feels polished, and the alignment of elements, especially the QR code and text, works well. It’s rewarding to see how consistent and visually appealing the result is. If I were to approach this project again, I’d focus on adding more detailed comments in my CSS to improve maintainability. I’d also prioritize testing on smaller screen sizes and adding additional media queries to ensure an even better mobile experience.

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

My biggest challenge was learning how to decipher the Figma file and translate the design into CSS. Understanding the spacing, font sizes, and layout properties in Figma and then implementing them accurately in code required a lot of focus and trial and error. To overcome this, I took the time to study the Figma interface and paid attention to the details, like margin and padding values, font weights, and colors. It was a learning curve, but breaking the design down into smaller, manageable parts really helped.

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

Specifically, I’d appreciate feedback on whether I accurately translated the Figma file to the web version. Did I effectively match the layout, spacing, font sizes, and overall visual design? I’d also welcome suggestions for any areas where the translation could be improved to better reflect the original Figma design.

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 jeffgrahamcodes'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

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.