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

Qr code component using html and css

Lalalaloo•40
@Lalalaloo
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 really proud that i was able to replicate the design.

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

I didn't know much about git or git-hub, since i am a beginner, but this project taught me. After hours of videos, i finally got it.

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

The entire code. Any feedback would be helpful

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Rohan T George•230
    @19Rohan97
    Posted 3 months ago

    Awesome work! You've replicated the design exceptionally well — great attention to detail and execution. It’s clear you’re developing a solid understanding of layout and responsiveness. Keep it up!

    📱 Suggestion: Embrace Mobile-First Approach

    I noticed that in your CSS, you’ve used max-width media queries, which means you're working from a desktop-first mindset and scaling down for smaller devices.

    Instead, I recommend switching to a mobile-first approach, which is the current best practice in responsive design.


    ✅ Why Mobile-First Is Better:

    • Performance: Mobile devices often have slower connections. Serving them a lightweight layout first improves load speed.
    • Progressive Enhancement: You start with the most basic version (mobile) and then enhance it for larger screens.
    • Maintainability: Writing base styles for mobile and layering min-width media queries for tablets and desktops is easier to scale and debug.

    💡 Example:

    Instead of this (desktop-first):

    .element {
      font-size: 24px;
    }
    
    @media (max-width: 768px) {
      .element {
        font-size: 16px;
      }
    }
    

    Go for this (mobile-first):

    .element {
      font-size: 16px;
    }
    
    @media (min-width: 768px) {
      .element {
        font-size: 24px;
      }
    }
    

    This way, you're building from the smallest viewport up — and letting styles grow with the screen size.


    Let me know if you want help refactoring your current CSS to follow this approach — I'd be happy to assist!

    Marked as helpful

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