Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive QR Code Component Using Flexbox

Mei Lee•40
@meillee
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Is there an alternative approach, other than utilising position: fixed;, to maintain the footer at the bottom of the page while simultaneously ensuring that the QR component remains vertically centered within the viewport?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • three•180
    @ewlondon
    Posted over 1 year ago

    In this instance, your main and div elements could be contained within a wrapper/container to solve this issue, allowing you to use grid to force their positions.

    article{
    	display: grid;
    	grid-template-rows: 1fr auto;
    	place-items: center;
            min-height: 100vh;
    }
    
      <article>
        <main>
        </main>
        <div class="attribution">
        </div>
      </article>
    

    This would eliminate the need for a position fixed on your footer attribution.

    Marked as helpful
  • aswinbhaskaran•60
    @aswinbhaskaran
    Posted over 1 year ago

    @meillee According to me, there is another way to implement it, but I am open to better options from others too.

    You can use about two display:flexs. The outer one can probably have justify-content:space-between;flex-direction:column while the inner one can probably have align-items:center. If there is enough space and it is also your preference, you can also add align-content:center, but you would need to add flex-wrap:wrap for it to work.

    This might make it look like the footer is at the bottom of the screen, while the QR code part is at the center of the screen. But the problem is width and height. While the width might not be as much a big problem, the height would be, considering different devices have different screen height.

  • Bishal Singh Deo🎮•1,440
    @Bishalsnghd07
    Posted over 1 year ago

    Hi Mei Lee

    Fantastic work🎉

    One suggestion from my side, never ever give height and width on a body, it only break your layout. So, my suggestion is to give min-height instead of height you used in body. In smaller project this is negligible but, when you work with larger project in future, then the layout will break if you use body { background-color: hsl(212, 45%, 89%); height: 100%;(use min-height: 100vh) font-family: "Outfit", sans-serif; justify-content: center; align-items: center; padding: 1rem; }

    And one more thing about using footer: Using footer fixed to bottom that is good practice, no need to change it

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub