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

QR Code component challenge

Olabisi G. Adekoya•70
@labisigloria
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first ever solution to a frontend mentor challenge, i had problems with creating the media queries for the challenge, i'm not even sure if the media query code i wrote is right according to the challenge, Please i'll appreciate a response on that and any other addition i should have made concerning my code.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • talisong-cardoso•100
    @talisong-cardoso
    Posted almost 3 years ago

    change:

    <meta name="overview" content="width=device-width" initial="" scale="1.0">
    

    to

      <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    

    and, you can centralize the ".box" with flexbox, exemplo:

    body {
        background-color: lightblue;
        display: flex;
        align-items: center;
        justify-content: center;
        height: 100vh;
    

    the width property in 'body' is not needed, as this small element is centered and will not 'exit' the viewport.

    sorry if there are any english mistakes. I'm from Brazil

    Marked as helpful
  • abdullah-mn•70
    @abdullah-mn
    Posted almost 3 years ago

    Hi ! you did good, but there are some small changes you can do to make it more good.

    • you don't need media query @media in this challenge. Remove the media query.

    • And also use flexbox to center the card, and remove the margin properties from body.

    • And always try to use min-height property, not height.

    I thin this comment will helpful. and Good luck to your upcoming challenges.

    Marked as helpful
  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    Hello Olabisi, congratulations for your solution!

    I've checked your code and I find an issue, when your card is scaling down, there's a big margin around the component that doesn't let it scale properly.

    See the fixes below:

    .box {
        background-color: hsl(0, 0%, 100%);
        width: 280px;
        /* height: 440px; */
        /* margin: auto; */
        border-radius: 15px;
    }
    

    Hope it helps, happy coding!

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.