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

Qr Code Component using HTML & CSS

Jesse Negrete•50
@JesNegrete
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This project was done using HTML & CSS. If I could have done anything differently please let me know. I'm always curious to see what other people came up with for their solution.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ana Milanezi•190
    @anamilanezi
    Posted about 2 years ago

    Hi Jesse, congratulations on completing this challenge!

    A simple improve can be achieved by simply defining a text-align: center for your <h1>.

    Other thing I've noticed is that you used a <div> to the wrapper container instead of the <main> which is a semantic HTML tag, and also left the alt attribute empty on your image. This are all related with the page accessibility, and are some details that I've actually started to pay attention thanks to the Frontend Mentor community and their feedbacks.

    Hope this can help you somehow! Congratulations again and keep going! 💪

    Marked as helpful
  • Ecem Gokdogan•9,380
    @ecemgo
    Posted about 2 years ago

    Some recommendations regarding your code that could be of interest to you.

    • You'd better remove margin from the body
    body {
      /* margin: 1.25rem; */
    }
    
    • When you use flexbox in the body, you don't need to use margin in the .container to center the card
    • If you use max-width, the card will be responsive
    • You can add text-align: center to center the texts
    .container {
      /* margin-bottom: 2rem; */
      max-width: 18rem;
      text-align: center;
    }
    
    • You can remove margin-bottom from the img
    .container img {
      /* margin-bottom: 2rem; */
    }
    
    • You can update margin in the h1 and add font-size to the texts
    .container h1 {
      /* margin-bottom: 2rem; */
      font-size: 1.3rem;
      margin: 1rem 0;
    }
    
    .container p {
      /* text-align: center; */
      font-size: 1rem;
    }
    
    • Finally, if you follow the steps above, the solution will be responsive. Additionally, you can remove media queries.
    /* @media (min-width: 500px) {
      .container {
        width: 400px;
      }
    } */
    

    Hope I am 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

Oops! 😬

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

Log in with GitHub