Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

QR Code page

Kauê Alves Vecchia•90
@kauevecchia
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?

Even with some bugs and some issues that I didn't know how to correct them, I searched for solutions and could get what I wanted

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

I had some issues and bugs, but I searched for solutions on stack overflow and I managed to fix it

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

Media queries and centralazing elements

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•7,030
    @R3ygoski
    Posted over 1 year ago

    Olá Kauê, parabéns pela conclusão do seu projeto, ele ficou muito bom.

    Começarei respondendo sobre media query, notei que no seu projeto não possui media queries, então acredito que a duvida que você tenha esteja relacionada ou a como se implementa ou se era necessário ou não, correto? Bom, caso seja como implementar uma media query, bom, você pode criar uma utilizando um @media (min-width: 1000px){}, entre os parênteses vai o escopo que você quer delimitar, e entre as chaves vai o estilo do escopo determinado, uma dica quando for usar isso, é a de utilizar o mobile-first workflow, que é, começar fazendo projetos nas telas mobile (320px ou 375px) e ir adaptando para telas maiores, pois essa forma é mais intuitiva e prática.

    Agora caso a pergunta era sobre se era necessário usar no seu projeto, na minha opinião sim, isso devido ao card ter ficado levemente cortado em 320px de largura de tela.

    Sobre centralização, existem várias formas, como margin: 0 auto;, position e por aí vai. As duas que eu mais recomendo que você foque são grid e flexbox, pois são bem mais fáceis e práticas. Deixarei alguns links a seguir sobre como você pode usar elas:

    • W3School - Flexbox(Obs.: Ao lado esquerdo tem os tópicos de Flexbox, navegue neles para ver sobre flexbox)
    • MDN - Flexbox
    • W3School - Grid
    • MDN - Grid

    E novamente, parabéns pelo seu projeto, caso algo que eu tenha dito não tenha ficado claro, ou que não tenha respondido as suas duvidas, por favor, deixe um comentário abaixo que tentarei responder da melhor forma possível.

    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

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