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

QR-code with CSS and HTML

Teo•30
@Teo-kodehode
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback would be greatly appreciated, and tips on how to make the padding between the picture and the white bg would be nice.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aditya Singh•460
    @adityas24
    Posted over 3 years ago

    Hey Teo! you did very well in your first challenge. I would like to suggest you the following....

    You could have avoided the div you used to wrap the h1 and p. As you have not used any style on div. Then you can simply avoid using it. It will not affect the semantics and will also decrease the length of the code.

    So you could simply write

    <div class="container">
          <img src="images\image-qr-code.png" alt="QR code">
          <h1>Improve your front-end skills by building projects</h1>
          <p class="text">Scan the QR code to visit Frontend Mentor and take your coding skills to the 
             next level</p>
    </div>
    

    All the best 🙂👍

    Marked as helpful
  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello there! Awesome work with this one. Viewing your solution I would suggest the following for you...

    • Inside the h1 rule set add margin: 0; and adjust the padding into padding: 1rem 2rem 0 2rem;
    • Same goes with .text add margin:0; and adjust the padding to padding: 1rem 2rem;
    • Instead of using div, wrap the container with specific tag like main for readability

    Hope this helps and Keep up the good work!

    Marked as helpful
  • Ken9Code•30
    @Ken9Kodehode
    Posted over 3 years ago

    Jævla bra jobba kompis! :D

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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