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

Eye-Catching QR Code Design: A Responsive HTML & CSS Showcase

ManoharDevangam07•10
@ManoharDevangam07
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 clean, responsive design of the QR code component. The use of modern CSS techniques ensures the component looks great on all devices, and the integration of Google Fonts enhances the visual appeal.

Next time, I would explore incorporating interactive features, like hover effects or animations, to make the QR code more engaging. Additionally, I’d experiment with more advanced layout techniques to further optimize responsiveness across various screen sizes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luka•180
    @zmora2622
    Posted 12 months ago

    The solution differs significantly from the design.

    First of all, in the html code, I would suggest using the h1 tag instead of h3, and the main tag instead of the section (good practice). I would not operate on vh sizes for widths as they are problematic. I suggest setting: html { font-size: 62.5%; } , then the font-size for the whole page will be 10px, allowing easy use of rem instead of vh.

    I suggest setting the colours as CSS variables, this makes it easier to change the colour scheme in larger projects.

    The whole card would look better with more rounded corners and more room to breathe inside (padding).

    The text to catch the eye should definitely be larger.

    Marked as helpful
  • tomblack9452•60
    @tomblack9452
    Posted 12 months ago

    This design follows the design brief correctly in terms of colour styling, however the sizing of the QR code and the text is different to the initial design. This newer one looks more pronounced and 'straight to the point' in my opinion (if this description makes any sense) with the slightly differing sizes, but in the real world it depends on exactly what the client is aiming for whether they'll accept that or not. CSS could be moved to an external stylesheet as well but for a page this small, it's irrelevant really.

    Great design and overall clean code too <3

    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

Oops! 😬

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

Log in with GitHub