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

QR code component solution

Bensolve•120
@Bensolve
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 the fact that I was able to structure the component using semantic HTML and style it cleanly using Flexbox with a mobile-first approach. It was satisfying to see everything centered properly and looking exactly like the design.

What I would do differently next time is:

-Add comments in my CSS to improve readability for others.

-Try implementing the layout using CSS Grid as well, to compare both methods.

-Focus more on accessibility — like adding proper alt text and considering screen reader users.

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

One of the main challenges I encountered was understanding how default browser styles (like margin and padding) affect layout. Elements didn’t line up as expected at first, but I learned to use a CSS reset and inspect the DOM to better control spacing.

Another challenge was getting the component perfectly centered on the page. Initially, I struggled with margin tricks, but I eventually solved it by using Flexbox and setting min-height: 100vh with justify-content and align-items to center the component both vertically and horizontally.

Lastly, I found it tricky at first to organize my CSS clearly, but using BEM naming conventions helped me write cleaner, more maintainable styles.

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

I’d appreciate feedback on:

CSS structure and best practices: Am I using BEM and Flexbox efficiently, or is there a better way to organize the styles?

Responsiveness: Does the layout hold up well across various screen sizes? Are there improvements I can make?

Readability of my code: Is my HTML and CSS clean and easy to understand, especially for someone else reading it?

I’m also open to general tips on improving my workflow or making future components more reusable and scalable.

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 Bensolve'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.