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

QR Code Component using pure HTML & CSS with Flexbox

puja oli•20
@puja-oli
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 this component with clean HTML and CSS. I kept the layout responsive and consistent across screen sizes. Next time, I might experiment with using CSS Grid or try adding transitions to enhance interactivity.

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

The most challenging part was aligning the component precisely on the screen while ensuring it remained responsive across various screen sizes. I used Flexbox on the <body> to center everything and added padding to improve responsiveness on smaller devices.

Another challenge was matching the exact color values and font styles from the design specifications. I double-checked the style guide and used tools like Google Fonts to make sure it matched closely.

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

I’d appreciate feedback on:

How I can improve my responsive design strategy

Whether my HTML structure is semantic and accessible

Anyways to improve the clarity or efficiency of my CSS

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Katherine-Kapinus•60
    @Katherine-Kapinus
    Posted 4 months ago

    Hello! Your code looks great ✨

    To make it look even closer to the layout, you could wrap the title and description in an additional container with a limited width and add some bottom margin for spacing.

    Also, in future projects, it might be more convenient to separate styles into a dedicated CSS file and apply styles via class names — this makes your code more reusable and easier to maintain in larger projects.

    Great work overall, keep it up! 🚀

  • DarGR02•10
    @DarGR02
    Posted 4 months ago

    Excelente solución

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub