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

QR code component

oLucasstein•30
@oLucasstein
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 proud i got it

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

no challenges at all

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

I would like help with the structure of css and html and the way i used the respositivity

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • jdrodriguez2707•170
    @jdrodriguez2707
    Posted 4 months ago

    Hi, @oLucasstein. Hope you're doing very well. Your solution is very good, congratulations! 🎉

    Here are a few things I think could improve it even further:

    • Semantic HTML: Since we’re building a reusable component, wrapping all the content inside an <article> tag would be a great choice. This tag is meant for self-contained content, making the card more adaptable. Plus, you could replace the <h1> with an <h2>, assuming the card will be used within a page that already has an <h1>. This is just my perspective, thinking about how the component might be integrated into a larger project, but feel free to keep the <h1> if it makes more sense in your case.

    • Accesibility: You could try testing your site with different browser font sizes to see if anything breaks. I’d recommend using 'rem' instead of 'px' for those elements that need to adapt to user preferences, especially text. This helps ensure that your design remains accessible and adjusts properly to different user settings.

    • Code structure: You should use classes instead of ids so you can reuse styles when necessary. Maybe in this small project we can't see a difference but we'll do in larger projects. So it's good to get used to it, in my opinion. And last but not least, you could also use CSS custom properties to store those repeated values like colors, font sizes, spacing, etc. This makes your styles more maintainable and flexible. For example:

    :root {
      /* Colors */
      --slate-300: hsl(212, 45%, 89%);
      --slate-500: hsl(216, 15%, 48%);
      --slate-900: hsl(218, 44%, 22%);
      --white: hsl(0, 0%, 100%);
    
      /* Typography */
      --primary-font-family: 'Outfit', serif;
      --primary-font-size: 2.2rem;
      --secondary-font-size: 1.5rem;
    }
    

    Overall, you did it very well and solved the challenge, that's the most important thing. This is just my personal opinion and recommendations that I can give you based on my own experience. Keep up the great work and happy coding! 🚀

    Marked as helpful
  • Carrinson•10
    @Carrinson
    Posted 4 months ago

    it looks really good and has good responsiveness

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