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

A simple and responsive QR code component

Usieme Blessing Onome•50
@usiemeblessing
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 the challenge from start to finish and applying what I’ve learned about HTML and CSS. I was able to create a clean and responsive layout that closely matches the original design. This project gave me more confidence in structuring content and using CSS to center and style elements effectively.

Next time, I would pay more attention to fine-tuning spacing and font sizes to match the design more precisely. I’d also like to explore using more modern CSS techniques, such as custom properties or utility-first frameworks like Tailwind CSS, to write cleaner and more reusable styles.

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

During this challenge, I found deploying the project and getting images to display properly in the README a bit challenging but eventually was a learning moment.

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

I’d appreciate help with making my layout more responsive across different screen sizes. While I was able to center the component on a larger screen, I’m not entirely confident in how to scale the layout effectively for smaller devices. Any guidance on using media queries or flexible units to improve responsiveness would be really helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • gabrielsf-dev•30
    @gabrielsf-dev
    Posted 3 months ago

    much better than what I did, I don't know what you could improve considering my beginner knowledge, it's beautiful

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