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

Basic QR-Code Card template using HTML and CSS

Vanshul Bhatia•10
@VanshulB
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How can we make the card for the iPad view i.e. width of the viewport is between 600px to 760px because the card looks very awful during that size because the QR image is just too big for that region?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Antoine C•1,240
    @mattari97
    Posted almost 3 years ago

    Hi Vanshul. Nice design. Congrats on completing the challenge.

    Like imad said you just need to use a fixed max-width for you qr-container.

    You'll also need to set the property width: 100% so the element always takes the maximum space available. This way you do not need any media query anymore.

    Example:

    .qr-container {
      width: 100%;
      max-width: 18.75rem;  /* 300px */
    }
    

    Then i would add some padding on the parent container so the qr-container does not stick to the sides of the window on small screen.

    Example:

    .container {
      background-color: hsl(212, 45%, 89%);
      width: 100%;
      /* height: 100%; */
      min-height: 100vh;
      display: flex;
      justify-content: center;
      align-items: center;
    
      padding: 2rem;
    }
    

    Again nice job and happy coding. Peace

  • imad•3,330
    @imadvv
    Posted almost 3 years ago

    Greeting Vanshul Bhatia!! Congratulations on completing Your challenge!, 👏👏👏 well done.

    to solve that issue, just replace width:80% to some more specific width, like max-width: 20rem;.

    example fix .

      @media only screen and (max-width: 768px)
    .qr-container {
      /*  width: 80%; */
      max-width: 20rem;
    }
    

    Hope this help!!

    over all, Happy Codding, and 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 1st-party linked stylesheets, and styles within <style> tags.

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.

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