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

Responsive QR Code Solution Using CSS Flexbox

MelissaZhuu•100
@MelissaZhuu
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'm proud of completing my first frontend mentor challenge. Although it was a simple one and I only used HTML and CSS, I learned a lot about CSS positioning and Flexbox and I feel more confident styling HTML elements moving forward. I also recently went back and fixed up my old solution, making it responsive so I'm pretty proud of this new solution. Next time, I would try to practice using a CSS preprocessor like Sass or a framework like Bootstrap or Tailwind.

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

I've always struggled with positioning HTML elements. I understood what Flexbox is but haven't actually applied my knowledge much in practice. Originally, I thought I had to combine Flexbox with absolute and relative positioning to position elements exactly how I wanted, however I soon realized that using absolute positioning kind of messed up the behavior of the card once the screen size shrunk. I went over my old solution and was able to find a way to produce the design with only Flexbox. I realized that I had to adjust the way I was thinking about positioning to the way Flexbox worked. I was too fixated about positioning the QR code 16px from the top of the container, which is why I thought absolute positioning made sense. Instead, since things were already centered in flexbox, I just had to adjust the spacing in-between components to push it more to the top of the container.

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

I know it's ideal to not use pixel values in order to make a website responsive. However, is it ok for border-radius to be in pixels or do people usually change that to a responsive unit as well?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on MelissaZhuu's solution.

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.