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

QR Code card using HTML and CSS

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

Solution retrospective


I would like to know how I can improve my CSS if possible. Another thing I am wondering is, when I add the text at the bottom as a footer, I would like for the card itself to still be at the center of the page, I was not able to figure out how to do that. Any help is appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Krzysztof Rozbicki•370
    @KrzysztofRozbicki
    Posted over 2 years ago

    Answering your question about the attribution. First be sure that your body has a

    position: relative;
    min-height: 100vh
    

    First needed so you can position the child of body according to its parent (body), second one is just to be sure that your body is at least as high as the viewport(screen) of user. Then in the attribution class you put e.g.

    position: absolute;
    bottom: 0.5rem
    

    Which means that your attribution will be always 0.5rem (default 8x) from the bottom of viewport You can read more about positioning - relative and absolute here: https://www.w3schools.com/css/css_positioning.asp And of course good old Kevin Powell: https://www.youtube.com/watch?v=P6UgYq3J3Qs

    And i advice you strongly to test that yourself by simple divs and just have fun and testing a lot of stuff. Positioning is in my opinion crucial to understand and without it is simply not possible to get the design look as you want.

    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