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

QR Code component using margins and flexbox

CristianoAAA•30
@CristianoAAA
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 really proud i figured out what i was going wrong in the preovious projects, but i would start from the top to bottom in the next projects.

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

I encountered challenges with the text, but i figured going a little bit of the rules doesn't matter so I went of the style guide to make the text look the same as the image in the solution. I encountered some trouble with the margins, but with a little bit of patience it got resolved. Also at inserting the image i got an unknown error, but after some digging i discovered it was a mistype.

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

I would like some help at how to insert images that when i deploy the website with vercel, the image still apear on the site, and not just desapear .

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar Dwivedi•720
    @Harsh-Kumar-Dwivedi
    Posted about 1 year ago

    Hi @CristianoAAA,

    I think as you have defined image source as images/image-qr-code.png in the HTML file, so, what you can do is, create a folder with name as images then add the qr code image to the folder with the name image-qr-code.png and then drop the images folder into the github repository of this project. This should resolve the issue of image not showing.

    Nice Work !

    Hope it is helpful !

    Happy Coding !

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