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

Responsive QR Code Component Using Flexbox

Jessica•70
@JesNetWD
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 think i nailed the vertical alignment if my main element which helps for a more responsive design across variou screen sizes.

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

In trying to properly vertically align my main element, i had a bit of a setback as i used different ways to try and properly center it such as position or margin-auto but flexbox worked the best.

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

I would like to know how to fix something at the bottom of a page. My .attribution element was fixed at the bottom of the screen using fixed position but for a vey small screen it could overlap with the other elements. I would like to know how to fix it to the bottom of the page like a page number or a footnote.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Paul•290
    @devPauloski
    Posted 3 months ago

    Well done. Your solution has semantic HTML included, and it is well-structured, but the responsiveness needs some fixing. I would recommend you do the following:

    • On the main HTML element, replace the 'width' property with 'max-width'. Remove the height set on it, you don't need that, let the content flow do its thing. Reduce the bottom padding to 20px. Set margin of 16px on the main to create some space on the edge of the layout for mobile screen.
    • Remove the padding set on the section HTML element.
    • On the footer HTML, remove every set CSS property, including the "position: fixed", and add a margin of 16px to have side alignment with the main on the mobile screen. Good Job!
    Marked as helpful
  • web-dev-pasta•790
    @web-dev-pasta
    Posted 3 months ago

    Great job!, for your question you can use a property called white-space so in your code you can use it like this :

    .attribution {
      white-space: nowrap;
    }
    

    I hope that helped!, 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.

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