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

QR component using CSS and HTML

Gus•60
@angusgee
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey folks!

  • The main div.container has been pushed up above the centre of the screen by the attribution section. How can I center it, please? I can't see why the attribution section makes it take up so much space? Neither div.container nor div.attribution have any padding or margin...
  • Is the shadow correct on the main div?
  • Is the use of CSS Grid to center the main div, then CSS Flexbox to centre the child items, correct? Or is there any easier way to create this 'single page, single element, everything centred' layout?

Appreciate you all! <3

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lord Robins•610
    @ZenitsuAg
    Posted over 2 years ago

    Hi MaltaWebDev, you've done an amazing job. Here are some tips to help you improve your code.

    • In the subheading class, it's better to add a h1 tag to wrap the text.
    • In the img tag, width=300 not 300px. But for responsive images in future, you can set the width to 100% or the max-width to 100% and it will scale down as automatically and it won't overflow the allocated space.
    • For the centering issue, you just add body {display: flex; justify-content: center; align-items: center;}
    • If the attribution div is causing you issues, you can just say position: absolute; bottom: 0

    So you may not really need to use CSS grid to center your code. Also, if you like the shadow, you can leave it but it's not really part of the original design.

    Happy Coding :)

    Marked as helpful
  • Edoye•170
    @DoyeDesigns
    Posted over 2 years ago

    Good work Lord robins!

    You do not need css grid to center the page Elements. You can add;

    Body { Display: flex; Min-height: 100vh; Justify-content: center; Align-items: center; }

    You can check how I did mine. I reduced the amount of nested divs by grouping some elements into one div.

  • Adriano•42,890
    @AdrianoEscarabote
    Posted over 2 years ago

    Hi MaltaWebDev, how are you? I really liked the result of your project, but I have some tips that I think you will enjoy:

    To improve the responsiveness of the project, we can do this:

    .qr-code img {
        border-radius: 20px;
        width: 100% !important;
        max-width: 300px;
    }
    

    I noticed that you used inline css to put width in the img prefer not to do that, we consider it a bad practice because in larger projects, there may be some conflict between the values ​​that we put in the html and in the css, and changing these values ​​in different files takes a lot of time!

    The rest is great!

    I hope it helps... 👍

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