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

QR Code Component | Frontend Mentor

ttvclvckPWNERS•30
@ttvclvckPWNERS
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?

For my project, I'm most proud of the functionality I was able to implement and the way the final product turned out. Seeing everything come together after all the hard work was incredibly satisfying. I learned a lot about problem-solving and how to overcome unexpected challenges, especially when it came to debugging and optimizing the code.

If I could do something differently next time, I would:

  • Focus more on planning and documentation from the start. I realized that having a more detailed plan and keeping better records of my decisions would have saved time and made the development process smoother.
What challenges did you encounter, and how did you overcome them?

For this project, I didn’t encounter any significant challenges since the task was relatively straightforward. The ease of the project allowed me to focus more on refining my CSS skills and paying attention to the details, like ensuring the layout was pixel-perfect and responsive.

While there weren’t any major hurdles, I did take the opportunity to experiment with different CSS properties and layouts. This exploration helped me solidify my understanding of CSS, and I feel more confident in my ability to tackle more complex projects in the future.

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

Since the QR Code Component project was fairly simple and I didn't face any major challenges, I don't need much help with this particular project. However, I’m always looking for ways to improve and would appreciate feedback on:

  • Code Optimization: Are there any areas where I could streamline my HTML or CSS for better performance or cleaner code?
  • Best Practices: Did I follow best practices in terms of structure, semantics, and accessibility? Any tips on improving in these areas would be helpful.
  • Design Enhancements: Are there any subtle design improvements I could make to enhance the user experience or visual appeal?

Getting insights on these aspects would help me refine my approach in future projects.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abd Ur Rehman•360
    @A-noob-in-Coding
    Posted 11 months ago

    Hi there

    Good job for this challenge, I would like to suggest some things regarding semantics

    For the card container you can wrap it in main section instead of a div

    <main> </main>
    

    Also while using images you can keep them in <figure></figure> for better semantics

    Hope you find my suggestions helpful 🥰

  • Dei•60
    @deidalopez
    Posted 11 months ago

    Awesome job, this looks great!

    Some really small pointers:

    • I noticed theres some divs nested around the same code "<div class="container"><div class="card"> ... </div></div>", could the styling be combined and only need 1 div instead of 2?
    • This is a small project, but for larger projects consider storing the colors from the design in variables so you can reuse them (reference: https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties)

    Keep up the good work!

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