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

qr code component

Mauricio Andrade•50
@mauricioandrade
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?

Acho que esse ficou mais claro, não tive muita dificuldade apesar de ser algo simples.

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

No começo esqueci que eu precisava dar um padding na imagem pra ela se ajusar na "div" que eu fiz do background, mas logo percebi e acabou dando certo.

What specific areas of your project would you like help with?

Sempre quero melhorar, qualquer sugestão para melhorar o código e deixar menos verboso tá valendo.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•6,950
    @R3ygoski
    Posted 8 months ago

    Olá novamente Mauricio, e novamente parabéns.

    Vou começar falando sobre isso que você mencionou do padding. Na verdade, o mais correto era colocar a padding no card, ou seja, no cartaoqr. Porque dessa forma você consegue dar o espaçamento correto para todos os items, e não deixa a padding "fragmentada" em cada elemento. E claro, isso também simplifica pois não precisamos ficar procurando por elemento X para mudar a padding dele quando alterarmos a padding de um elemento Y.

    Caso você remova a padding de todos os elementos e deixe só no cartaoqr, lembre-se de adicionar também ao cartaoqr um gap: 1.5rem, que assim deixara os elementos espaçados.

    Sobre o HTML, mesma coisa que falei da semântica no projeto de NFT, mas dessa vez, o único elemento que poderia ficar mais semântico é div.cartaoqr, que poderia ser uma <article>, explicação também no projeto de NFT.

    E é isso, novamente parabéns, caso tenha ficado qualquer dúvida, já sabe.

    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