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

QR HTML and CSS only :)

Leon•20
@Codelon2
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm having difficulties with sizing the white box. i dont know exactly what height it should have.. because in the picture you guys provide it seems a bit longer... more a rectangular form, and mine is more squarish

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Paula•60
    @thedoodlebakery
    Posted over 3 years ago

    It looks good. Try playing around with your padding for the white box. Probably adding more padding to the top and bottom vs the left and right. Start someone where with something like padding: 10px 15px; The first number in that style is the top and bottom and the second number applies to the left and right.

    Marked as helpful
  • Andy•520
    @AndyAshley
    Posted over 3 years ago

    I agree with what Paula said. It looks really good. The padding is most likely the issue going on. you can wrap the text in a div and give it some padding on the left and right. You could do something like:

    padding-inline: 15px;

    you can check my code to see how I dealt with the layout. Mine isn't as tall either.

    Marked as helpful
  • Abdul•8,560
    @Samadeen
    Posted over 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. . Here are my suggestions 1.You should use <main class="white-bg"> instead of <div class="white-bg">. 2. Go down orderly when you are using the headings h1 down to h2 down to h3 and so on. 3. You should maybe reduce the padding on both left and right of your card

    . Regardless you did amazing.. 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

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