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

Projeto feito com HTML e CSS básico.

PatrickDzS•20
@PatrickDzS
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 posso dizer que por mais simples seja o projeto, pode ser feito de diversas formas e optei por fazer da forma mais básica por falta de conhecimento ainda em css grid por exemplo, então me orgulho de ter feito o projeto mesmo que de forma simples.

Gostaria de mais a frente com mais conhecimento, aplicar de forma mais avançada outras formas e refazer o projeto.

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

Acredito que aplicar meus conhecimentos para conseguir fazer o projeto, mas fiu superado com o conhecimento que tinha e através de pesquisa.

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

Gostaria de ajuda para desenvolvimento com outra técnica, talvez mais avançada para ter esse conhecimento também e poder aprender mais sobre a tecnologia e suas formas de realizar o projeto.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Danyal•50
    @imRanDan
    Posted about 1 year ago

    QR code looks great from preview. I would say it may not follow the exact measurements from the Figma file, but other than that, it looks great!

    for your HTML, I noticed you used divs mostly. This is okay for getting the first draft/rough copy done, but for improving i would recommend to follow a semantic layout. for example: you could use sections and a header/footer to contain your "built by" message.

    CSS looks great! It is responsive for the most part. I would recommend for Mobile screens to center the QR code.

    Well done!

    Marked as helpful
  • PatrickDzS•20
    @PatrickDzS
    Posted about 1 year ago

    Obrigado pelas considerações, será muito positivo para a minha evolução, vou estudar mais e darei mais atenção a semântica que de fato faltou.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub