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

- Using CSS and Flexbox to center elements horizontally and vertically

Amhed Hussien•390
@Eng-Ahmed-Hussien
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 most proud of how clean and minimal the design turned out, closely matching the original challenge. The use of Flexbox for centering and CSS calc() for dynamic spacing made the layout both responsive and easy to manage.

Next time, I would consider enhancing accessibility by improving the contrast ratio and adding ARIA attributes for better screen reader support. Additionally, I might experiment with CSS Grid to explore different layout techniques and ensure the design adapts seamlessly to various screen sizes.

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

ne of the main challenges was centering the QR code component properly on all screen sizes, especially handling vertical alignment. Initially, using only margin: auto didn’t work well for full-page centering, so I switched to Flexbox, which made it much easier by using align-items: center and justify-content: center.

Another challenge was ensuring the layout remained consistent on smaller screens. To solve this, I used min-height: calc(100vh - 50px), which helped maintain proper spacing while preventing unwanted overflow.

By testing across different devices and adjusting the styles accordingly, I was able to create a solution that is both visually appealing and responsive.

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

I would love feedback on the following areas:

Responsiveness:

Are there any improvements I can make to ensure the design adapts even better to different screen sizes? Would using CSS Grid instead of Flexbox be a better approach for this layout? Accessibility:

Are there any ARIA attributes or semantic improvements I should add to make the QR code component more accessible? Code Optimization:

Is there a more efficient way to structure my CSS to improve maintainability and reduce redundancy? Any best practices I might have missed?

I appreciate any suggestions to refine and improve my solution further! 🚀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • taciasales•20
    @taciasales
    Posted 6 months ago

    I found your solution very interesting.

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