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

QR Code component

ROAR•70
@R04R1NG
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?

As a beginner, I created several divs and CSS selectors on my first attempt. I realized that this approach was inefficient, so I decided to read and watch tutorials on HTML and CSS. On my second attempt, I managed to reduce the number of lines by grouping elements more efficiently.

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

I am not yet familiar with CSS variables, so I ended up going back and forth with the style guide to ensure accuracy and achieve a pixel-perfect design. If I had used CSS variables, it would probably have sped up the process. I’ll make sure to implement CSS variables in my future projects.

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

So far, I have not encountered any major issues in this project. However, with my limited knowledge, this path feels a bit unclear, and I’m not sure what questions to ask yet. I’ll continue to explore and learn so that I can seek feedback and guidance on specific areas in future projects.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Natali 👻 Grimm•1,190
    @Grimm-N
    Posted 9 months ago

    Your work is looking fantastic—seriously, keep it up! 🌟 Every step forward shows your dedication.

    Here are a few pointers to make it even better:

    1️⃣ Pixels? Try switching to em, rem, or % instead. They’re way more flexible and adapt beautifully to different screen sizes. This helps your designs stay consistent across devices. 📱✨

    2️⃣ On smaller screens, set your card width to 90vw or 90%. This keeps it clean and prevents it from sticking awkwardly to the edges. It’s a game-changer for responsive layouts! 🖼️

    3️⃣ Always give your elements classes! It makes your code more manageable and readable. Plus, following the BEM (Block-Element-Modifier) method keeps everything structured. Example:

    <div class="card card__image card__image--highlighted"></div>
    

    BEM keeps your styles clear and scalable, especially as your project grows. 🚀

    Keep up the amazing work—you’re absolutely smashing it! 💪🎉

  • TGF•80
    @thecodefan
    Posted 9 months ago

    This design looks solid! i also had problems with using too many divs, and my positions were inefficient at best, though they got the job done, hopefully i can fix it up like you have in the future.

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.

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