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

QR CARD CSS FLEXBOX

RoxySash•180
@RoxySash
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 am proud that I completed this. It took a while but its complete.

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

I couldn't figure out why there is a scroll bar. It was hard to structure all the divs I made.

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

Flexbox and centering elements

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Zugim•80
    @Zugim
    Posted 9 months ago

    It looks great! Apart from the sizing it is looking super close to the original design.

    To maybe fix the sizing I would look at removing the div blue-area-behind and instead applying the blue background colour directly to the body. If you then make the body display property flex hopefully you will be a bit closer to the original design.

    It's worth noting that children of elements that display as flex automatically become flex-items so should shouldn't need to set all of your elements to display flex.

    When I was first learning flexbox this course by Wes Bos really helped me out.

    https://flexbox.io/

    Really good job! Keep it up 👍

  • Eduardo Santos Ferreira•10
    @eduardo5010
    Posted 9 months ago

    The result is very good, only the page size is apparently smaller than the original design. Sorry for my bad English.

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