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

QR code using CSS grid system

nco0305•10
@nco0305
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?

The way how it turned out

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

I could not use and centre the flex box, so I tried the grid as an alternative.

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

Any other alternative ways to create the same component? I can't figure out why the image shows broken in GitHub live page link.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted 10 months ago

    Hey, @nco0305! I noticed a few errors in your code that you can improve:

    • Make sure to add <img src="./Images/image-qr-code.png" ...>. This tells GitHub to look for a folder named "Images" in the root directory and pull out the image named "image-qr-code.png" (the period(dot) is important).

    • The box-shadow: 15px; declaration is invalid. Try something like box-shadow: 15px 15px 0 0 blue;. The box-shadow property requires values for offset, blur radius, spread radius, and color; you haven’t set values for all of them.

    • padding: 0, 40px, 40px, 40px; is invalid due to the commas. Replace the commas with spaces, like this: padding: 0 40px 40px 40px;. Remember, padding values follow the order: top, right, bottom, left.

    • When using margin: 0%;, you can simply write margin: 0;. The browser will understand, and this helps save some time.

    Everything else looks perfectly structured. Great job!

    I hope you find this helpful.

    Marked as helpful
  • JL10•260
    @JLizcano10
    Posted 10 months ago

    Hello, the QR image is not displaying because web servers are usually case sensitive. Currently, you are using a lowercase “i” in the image font:

    <img src=“images/image-qr-code.png” />

    However, the repository folder is named Images with an uppercase “I”. To fix the problem, you can either rename the folder to images or update the image source path in your code to:

    <img src=“Images/image-qr-code.png” />

    This should solve the problem.

    Marked as helpful
  • Meryem El Karati•150
    @Cristal32
    Posted 10 months ago

    It seems the issue with the image not showing up is the the path:

    In index.html:

    <img src="images/image-qr-code.png" alt="QR Code" width="280" height="280">

    It should be :

    <img src="Images/image-qr-code.png" alt="QR Code" width="280" height="280">

    since the name of the correspondant folder is 'Images' with a capital I

    Marked as helpful
  • Bart Feesley•220
    @antimatterhut
    Posted 10 months ago

    When I preview your site, the qr picture does not show up.

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, SASS, 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

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