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

qr-code-component-main

Raphael Siqueira•150
@raphaelsiqueiira
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?

Estou orgulhoso de como as variáveis CSS ajudaram a organizar meu código de forma eficiente, facilitando as atualizações e mantendo uma consistência visual. Para otimizar ainda mais o desempenho, utilizei a minificação de CSS para reduzir o tamanho dos arquivos, garantindo tempos de carregamento mais rápidos e uma experiência de usuário mais ágil. Essa combinação de técnicas resultou em um projeto mais eficiente e profissional, algo que planejo repetir em projetos futuros.

I'm proud of how CSS variables helped organize my code efficiently, making updates easier and maintaining visual consistency. To further optimize performance, I used CSS minification to reduce file sizes, ensuring faster loading times and a smoother user experience. This combination of techniques resulted in a more efficient and professional project, something I plan to replicate in future projects.

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

Não enfrentei grandes desafios durante este projeto. A familiaridade com as tecnologias e a clareza dos requisitos tornaram o processo de desenvolvimento bastante tranquilo. Isso me permitiu focar na implementação das funcionalidades e na criação de um design atraente. Ao seguir uma abordagem iterativa e organizada, consegui avançar de maneira eficiente e alcançar os objetivos estabelecidos para o projeto. Essa experiência me permitiu consolidar meus conhecimentos e fortalecer minha confiança como desenvolvedor.

I didn't face significant challenges during this project. Familiarity with the technologies and clarity of the requirements made the development process quite smooth. It allowed me to focus on implementing features and creating an appealing design. By following an iterative and organized approach, I was able to progress efficiently and achieve the project's established goals. This experience allowed me to solidify my knowledge and strengthen my confidence as a developer.

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

Como iniciante na programação, gostaria de receber feedback sobre melhorias e possíveis alterações no projeto, especialmente em áreas como organização do código, boas práticas de codificação e otimização de desempenho. Qualquer orientação sobre como melhorar minha abordagem de desenvolvimento e elevar a qualidade do projeto seria muito apreciada.

As a beginner in programming, I would like to receive feedback on improvements and possible changes to the project, especially in areas such as code organization, coding best practices, and performance optimization. Any guidance on how to improve my development approach and elevate the quality of the project would be greatly appreciated

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Raphael Siqueira's solution.

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.