Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Componente de QR Code feito usando HTML e CSS

Lucas Volpato•10
@Luccas71
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Por mais simples que seja, foi a primeira coisa que eu fiz com meus proprios recursos, sem um tutorial passo a passo

What challenges did you encounter, and how did you overcome them?

centralizar o componente sem usar flexbox

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • benssssss•380
    @benssssss
    Posted 5 months ago

    Olá, vi seu código e vou sugerir algumas alterações.

    Você poderia colocar seus textos (h1 e p) dentro de uma div, assim como fez com a imagem, e então aplicar um padding diretamente nessa div, em vez de colocá-lo nos textos individualmente. Isso tornaria seu CSS mais limpo.

    Notei que você usou translate para centralizar o cartão, o que funciona, mas não é a melhor abordagem, na minha opinião. Como você está aprendendo, pode não ter tido contato com display: flex;, que facilita muito o posicionamento dos elementos com menos código.

    O que eu faria é:

    1 - Remover a centralização do .card

    .card { 
        /* position: absolute; */ /* remover */
        /* top: 50%; */ /* remover */
        /* left: 50%; */ /* remover */
        /* transform: translate(-50%, -50%); */ /* remover */
        /* margin: auto; */ /* remover */
    
        width: 300px;
        border-radius: 20px;
        background-color: var(--white);
    }
    

    2 - Definir e centralizar o .card usando flex

    body {
        /* max-width: 1444px; */ /* remover */
    
        font-family: Outfit, Arial, Helvetica, sans-serif;
        background-color: var(--slate-300);
    
        display: flex;
        justify-content: center;
        align-items: center;
        height: 100vh;
    }
    

    display: flex; define o body como um contêiner flexível.

    justify-content: center; centraliza o .card horizontalmente.


    align-items: center; centraliza o .card verticalmente.

    Porém, por padrão, o body tem a altura do conteúdo (neste caso, o .card, que tem 466px). Se aplicarmos align-items: center;, nada mudará, pois o conteúdo já está no centro do body. Para resolver isso, adicionamos height: 100vh;, que define a altura do body como 100% da tela do dispositivo, garantindo que o .card fique exatamente no meio da página.

    Seu HTML é semântico e seu CSS está bem organizado.

    Parabéns pelo primeiro projeto!

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