Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

QR Code challenge

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

Solution retrospective


Hello everyone! I would like to showcase my very first challenge here. I believe the result is faithful to the original. I had some issues with the font size. The prescribed 15px seemed a bit small to me, but it turned out that the 'container' div itself was larger than the original.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yonten•340
    @yozidst
    Posted over 1 year ago

    Hello,

    Congrats and Great job on your 1st Challenge! 👍

    I would recommend the following for laying out your content for the future. This way you won't have to center the container using margins or padding and the full height of the screen is utilized.

    eg.

    body {
        margin: 0;
        padding: 0;
        min-width: 100vw;
        min-height: 100vh;
        display: flex;
        justify-content: center;
        align-items: center;
    }
    

    Also, after setting your body's font size, you can make use of rem to scale the other differing components.

    • This means that 1rem equals the font size of the html element, which for most browsers has a default value of 16px.
  • P
    Øystein Håberg•13,260
    @Islandstone89
    Posted over 1 year ago

    HTML:

    • You need a <main>, this is important for accessibility. In such a simple component, it can also be the card, so change .container into a <main>.

    • The alt text also needs to say where it leads (frontendmentor.io).

    • .attribution should be a <footer>.

    • Footer text needs to be wrapped in a <p>.

    CSS:

    • It's good practice to include a CSS Reset at the top.

    • Font-size must never be in px. Use rem instead.

    • Remove the fixed width and height. You rarely want to set fixed dimensions, as this easily creates issues with responsiveness.

    • Give the card a max-width of around 20rem, so it doesn't stretch too wide on bigger screens.

    • On the image, add display: block and replace width with max-width.

    • Instead of using marginon the card itself, a more common way to center something in the middle is to use Flexbox on the parent of what you want to center. In this example, the parent of the card is the body:

    display: flex;
    flex-direction: column;
    justify-content: center;
    align-items: center;
    min-height: 100vh;
    

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