Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive QR-Code Grid Card || HTML & CSS

Krishna Rawat•20
@Krishnarawatethic
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 would like to design first then make because sometimes paremeter issue I have noticed from my end so far.

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

The challenge was to center the card container to the center but I then managed to make it center plus responsive.

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

The areas to create a design using Figma is challenge since my laptop hangs due to less RAM and memory which already is running VS Code and browser in behind.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • beowulf1958•1,930
    @beowulf1958
    Posted about 1 year ago

    Congratulations on completing this challenge. It looks good so far.

    I have a few suggestions. First, your image isn't loading. This is because you left off the file extension. Try this instead: <img id="img" src="images/image.png" alt="QR code to Frontend Mentor"> Note that you should always have an alt value in case the image doesn't load.

    Next, you can make it look more professional by giving your page a title instead of just "Document", something like: <title>Frontend Mentor | QR Code Challenge</title>

    Lastly, you can include the Frontend Mentor logo on the browser next to the title by adding a link in the <head> section: <link rel="icon" type="image/png" sizes="32x32" href="images/favicon-32x32.png">

    Hope this helps. And keep on coding!

    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