Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 days ago

Qr component challenge using HTML, CSS

P
Sina•30
@WebDevSina
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 am proud of how i was able to make it look similar. it's not perfectly identical but it looks okay to me.

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

The challenging part was trying to get the text looking right. it kept misaligning and I was able to use padding to get it right.

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

I would love help with my unit usage. I feel very uncertain about when to use what units.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amna Ashraf•850
    @Dev-Amna
    Posted 10 days ago

    🌟 You’ve done a really nice job on this QR code component! The layout is centered perfectly using Flexbox inside the .container with display: flex; justify-content: center; align-items: center, which gives it a very clean and balanced look. I really liked how you used color variables like --slate300 and applied it as the background using background-color: var(--slate300) — this is a great way to keep your theme consistent.

    🖼️ Your .main-container has a neat white background with rounded corners using border-radius: 20px and a max-width of 275px, which makes the card compact and stylish. The QR image is fully responsive because of width: 100% and height: auto, and the rounded corners are a nice touch with border-radius: 10px.

    📌 Just a small HTML issue: inside your .description, the <p> tag is incorrectly closed after the </div>. You should move the closing </p> right after the paragraph text to fix the HTML nesting. So instead of placing it outside the block, it should look like: <p>Scan the QR code to visit Frontend Mentor and take your coding skills to the next level</p>.

    📱 For better responsiveness on small screens, you already used a media query — which is awesome. Inside that media query (@media (max-width: 375px)), you could add width: 90% to .main-container so it scales better on mobile. It would look like this: .main-container { width: 90%; }.

    🎨 Another suggestion is to center the description block completely by adding margin: 0 auto in your .description CSS — so it becomes .description { margin: 0 auto; }. This ensures everything inside remains visually aligned.

    💡 And to make the card stand out more, you can apply a light shadow using something like box-shadow: 0 10px 25px rgba(0, 0, 0, 0.1) inside .main-container.

    📏 Lastly, for better font scaling on different screen sizes, you can use clamp() on your heading like this: font-size: clamp(1rem, 2vw, 1.3rem) inside your h1 styling.

    ✅ Overall, it’s a very well-done solution — clean layout, consistent styling, and great use of fonts and spacing. Just a couple of small improvements and it will be perfect! Keep up the great work! 🚀💻

    Marked as helpful

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