LBLenin Boccardo
InícioSobreProjetosContato

Command Palette

Search for a command to run...

Lenin Boccardo

Desenvolvedor Fullstack versátil com mais de 3 anos de experiência projetando, desenvolvendo e implantando aplicações web modernas em JavaScript, TypeScript, React, Next.js e Node.js. Forte expertise em infraestrutura AWS, backend com NestJS e Prisma, e liderança frontend para plataformas SaaS escaláveis. Reconhecido pela capacidade de resolução de problemas, adaptabilidade e práticas de código limpo, combinando bases técnicas sólidas com excelentes habilidades de comunicação.

Links Rápidos

SobreProjetosContato

Conectar

GitHubGitLabWhatsAppTelegram

© 2026 Lenin Boccardo. Todos os direitos reservados.

Desenvolvido com Next.js · Tailwind · shadcn/ui

Voltar para Projetos
Developer Portfolio

Developer Portfolio

Next.jsTypeScriptTailwind CSSReactAWSGit

This portfolio website showcasing projects and writeups with multilingual support, 3D animations, and optimized performance.

Ver CódigoDemo ao Vivo

Detalhes do Projeto

Status
Em Andamento
Linha do Tempo
2024-06
Tecnologias Utilizadas
Next.js, TypeScript, Tailwind CSS, React, AWS, Git

Overview

This portfolio is the site you are reading right now. It exists as both a personal showcase and a working sandbox for modern Next.js and frontend ergonomics.

Highlights

  • Internationalization across English, Portuguese, and Spanish — every URL slug is locale-aware (/projects, /projetos, /proyectos) via next-intl.
  • MDX-driven case studies — project pages like this one are authored as Markdown with frontmatter, kept under version control next to the code.
  • Server Actions + Zod validation for the contact form, with AWS SES for transactional email.
  • Presigned S3 downloads for resource files, never exposing static URLs to the client.
  • Edge-rendered OG images generated per page via @vercel/og.

Architecture decisions

The stack is intentionally boring where it can be — Next.js App Router, React Server Components, Tailwind v4 — and intentionally interesting where it matters: a 3D hero scene, a particle background, and a command palette. The lib/ layer keeps env validation, MDX loading, and AWS service singletons in one place so API routes stay thin.

What's next

Continuous improvement: more case studies, structured data for search engines, and analytics so I can tell which writeups actually resonate.