Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

QR code component solution using CSS Grid and Flexbox

Aliyu-Saidu•220
@Aliyu-Saidu
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


1- Please help. My finished project is not displaying correctly from the github live site url above! At first I forgot to include the image file in my file uploads but later added it in the github. I tried to refresh the page but did not work even though the finished project is now displaying correctly in my laptop after updating the file path in the 'src' attribute in the source code.

2- I am getting the following errors and whenever I try "git add ." in Git Bash. So I couldn't add, commit and push my codes from local machine to git hub. I had to resort to manual method! I have the following file types in my folder: .png, .gitignore, .html, .md and .css

warning: in the working copy of '.gitignore', LF will be replaced by CRLF the next time Git touches it error: unable to write file .git/objects/d1/3464af54e87679bf87e20754a35abe51dc4449: Filename too long error: .gitignore: failed to insert into database error: unable to index file '.gitignore' fatal: adding files failed

Now questions related to the project

1- I find it difficult to control the size of the image in its container using only template-columns and template-rows properties in grid without specifying image size in any unit. Please how best should I do it?

2- Please what is the difference between section, article and aside semantic tags in html?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • michaelbulaongdev•170
    @michaelbulaongdev
    Posted over 2 years ago

    Hi,

    Looking at your repository, the image file is located in your root folder. However, in your index.html, it is still routing from the "images" folder.

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

    Either add an "images" folder in your repository root then move the image file into that folder, or edit the <img src=""> in your index.html in order to fetch the image file from the correct address.

    Then re-run the build to deploy changes in your live site.

    I hope this feedback helps.

    Happy 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
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