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

HTML5 & CSS3 ,Flexbox,Responsive Design ,Google Fonts ,Git & GitHub,

Sujit Dhar•50
@sujitdhar014
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?

1)Responsive Design: I’m proud that the project adapts smoothly across different screen sizes, especially for mobile (375px) and desktop (1440px). Using Flexbox and media queries, I was able to center the card and make sure the layout looks great everywhere.

2)Attention to Detail: I followed the design spec closely, using HSL color values and a custom Google font (Outfit). The card’s padding, border-radius, and box-shadow create a polished look, matching the original design.

3)Clean Code: I’m happy with how I structured my CSS to be modular and easy to read. I used semantic HTML to ensure accessibility.

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

Issue: One of the biggest challenges was ensuring that the layout looked perfect on both mobile and desktop. Since the design had specific widths for mobile (375px) and desktop (1440px), I had to make sure the QR code card was centered and responsive on all screen sizes.

Solution: I used Flexbox for centering the content and applied media queries to adjust the layout for different screen widths. I tested the layout across multiple devices and screen sizes to ensure it was fluid and responsive. For smaller screens, I used max-width to prevent the card from becoming too wide.

What specific areas of your project would you like help with?
  1. Mobile Performance Optimization: Guidance on further optimizing images and resources for faster load times on mobile devices.

  2. Accessibility Enhancements: Suggestions for improving accessibility, especially for users with visual impairments.

  3. Multi-Project Deployment: Advice on managing and deploying multiple frontend challenges or a portfolio on GitHub Pages efficiently.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marko Stankovic•300
    @Stankovic77
    Posted about 2 months ago

    good one

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