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

QR code component

Soulchildpsalmy•60
@Soulchildpsalmy
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?

Writing this independently and understanding the concept of grids and flex elements

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

I had challenges pushing to github and publishing the page on vercel. with the support of a friend, I was able to get a hang of it.

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

I still need understand media queries better.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Edlitamis•40
    @edlitamis
    Posted 6 months ago

    Here are some improvements suggestions regarding the index.html file:

    • l24-26: you don't need to put the <img> tag within a <div> tag. The <img> tag is its own object in the sense that you can target it as is in you CSS file (you're doing it when targeting qr-image). Actually if you check the CSS file, the image class is never called or used, proof that it's useless.
    • l28: you have an <h2> but no <h1>. A good practice is to not skip heading levels: always start from <h1>, followed by <h2> and so on (check HTML heading documentation for more info).

    Code improvements in the qrcode.css file:

    • The CSS style file naming convention is styles.css.
    • l59-61: I think you can add padding to the container element so that the top doesn't crop when you shrink the screen size. Your updated code would then look like this:
        .container {
            width: 90%;
            height: auto;
            padding: 20px;
        }
    

    Apart from that I would say the code is good and readable and your solution looks like the design solution, keep it up 💪

    I am not an expert myself but I hope it helps 😊

    Marked as helpful
  • NossPro•30
    @NossPro
    Posted 6 months ago

    La sementique HTML est correctement respecter elle est accesible oui je trouve que certaine ligne de code n'ont pas lieu d'être ça charge pour rien le code oui la mise en page ça va oui pour les trois non je ne pense pas

  • Sawmail•10
    @shamel-rai
    Posted 6 months ago

    Great Work

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

Oops! 😬

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

Log in with GitHub