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

QR Elements designed using vanilla CSS

pure-css
HShambuck•40
@HShambuck
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 that, despite it being my first time tackling a challenge like this, I managed to get started and successfully build the project using vanilla CSS. It felt rewarding to dive back into CSS after a long break from coding with it.

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

When I started this challenge, I faced an issue identifying the main outline or div within the body. The problem stemmed from the image in the top layer of the parent div being too large. To troubleshoot the layout, I temporarily applied a red background to the parent div. To my surprise, it only highlighted the second layer (the QR details), leaving me confused. After some thought, I realized the issue was with the image size. Setting the image width to 100% resolved the problem perfectly.

The biggest challenge, however, was centering—particularly vertical centering. For horizontal centering, I initially used margin: auto, which worked well. But for vertical centering, I tried using align-items and couldn’t figure out why it wasn’t working. After several attempts, I discovered the problem: I was applying align-items to the child div instead of the parent div, which had the display: flex property. Once I applied align-items to the correct parent div, it worked perfectly. Additionally, I replaced margin: auto with justify-content for horizontal centering, achieving consistent and clean results.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Md Nazmus Shakib•10
    @nshakib
    Posted 6 months ago

    Your site is not live able.

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