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

Responsive QR Code Component Design

Ibrahim•30
@Ajibose
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 designed it using a mobile first approach. in my next project, i will like to experiment with CSS Grid instead of flexbox for centering and layout control to compare the flexibility and simplicity of each approach.

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

Initially, I struggled to vertically center the .main-container for larger screens. i thought using margin: auto; will automatically center vertically as well but later found out thatit has to have a defined parent height.

Solution: I switched to using Flexbox on the body with align-items: center and justify-content: center, which solved the issue.

i also had issue with knowing the size to use for an average size mobile

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

Are there better ways to ensure the design remains consistent on even larger screens because i noticed that the design seems a bit off for some screen size

Could I improve how i’ve used media queries to handle responsiveness more efficiently?

Am I following best practices for accessibility? For example, is the alt text in my <img> tag descriptive enough? and are there other things i could add to make the page more accessible

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • tortaruga•790
    @tortaruga
    Posted 6 months ago

    hi! i think the reason it looks weird on bigger screens is because on screens larger than 768px the width of .main-component is set to 15%, which is a bit small. you can try playing around with other percentage values, or even setting a fixed value like 320px, until you are satisfied with the way it looks. the rest is looking good, keep it up!

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