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

QR static card using HTML CSS

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

Solution retrospective


Any idea to how could I improve my code?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Acme Gamers•295
    @AcmeGamers
    Posted about 3 years ago

    Hey there 👋,

    Congratulations on completing the challenge 🎉! I really liked the way how you used width: min(30rem, 100%); to size the card's background 😀.

    Also, here are some ways through which you can improve your code more:

    Semantic HTML

    Semantic HTML improves the SEO of the website by giving more meaning to your HTML code, and it is a good practice to wrap all of your frontend code inside a <main> tag. In your case, it will go as:

    <main>
         <div class="contenedor">  ... </div>
         <p class="attribution">  ... </p>
    </main>
    

    Centering Elements

    For centring elements on the screen, there are 3 ways from which we can do so with ease, and for this one, I will go with flexbox. Now considering you have added the <main> tag into your code, we normally do this:

    .main {
         min-height: 100vh; // Catches full screen-height and can expand when more content is added
         display: flex;     // Flexbox
    
         flex-direction: column;     // Aligns your elements vertically [ div and p tag ]
         align-items: center;        // Center Elements Horizontally
         justify-content: center;    // Center Elements Vertically
    }
    

    This way, you won't need to use margin: 12.5% auto; on the contenedor class, helping you to align other elements more properly. You can try adding each line at a time from the above CSS code to understand how the flexbox works.

    Looking forward to seeing your amazing work in the future and hope this helps 😊

    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, SASS, 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