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

Desafio do QRCODE

cube-css
Mateus Wenzler•10
@WpMateus
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Primeiro Desafio Front-End Mentor / QRCode

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elio Flores•400
    @elioflo
    Posted over 2 years ago

    Hi there! Your solution looks good.

    I noticed that you used margin to center the .conteudo class div, but if the viewport height is too short, the .conteudo div may not look centered anymore. The Both Horizontally & Vertically css-tricks section on css-tricks has some advice and alternatives for centering elements.

    In your case, you could try using the following code to center the .conteudo div:

    .container {
        display: grid;
        min-height: 100vh;
        place-items: center;
    }
    

    This method will ensure that the .conteudo div is centered for any viewport height size.

    You're doing a great job with your coding. I hope this comment helps you improve your solution!

    Elio Flores

  • Finney•3,010
    @Finney06
    Posted over 2 years ago

    Hello there 👋. Good job on completing the challenge !

    Here are some suggestions regarding your code that may be of interest to you.

    HTML 🏷️:

    To clear the Accessibility report:

    • Wrap the page's whole main content in the <main> tag.

    • Use HTML5 semantic elements such as <header>, <nav>, <main>, <aside>, and <footer> to define these sections.

    Here is a web accessibility evaluation tool📕 to check your webpage for any remaining errors or warnings related to landmarks.

    I hope you find it helpful!😏 Above all, the solution you submitted is 👌. 🎉Happy coding!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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