JK
>ŁADOWANIE // ŁADOWANIE
INICJALIZACJA WIDOKU
Completednextjsreacttypescripttailwind
Portfolio Jitin K
Portfolio inżyniera full-stack prezentujące mikroserwisy, systemy rozproszone oraz nowoczesny frontend.
Problem i rozwiązanie
Stworzenie wyjątkowego doświadczenia wizualnego z płynnymi animacjami i wysokimi wynikami Core Web Vitals.
Funkcje
- Next.js App Router z next-intl w 9 językach
- Interaktywne diagramy architektury w React Flow
- Kinetyczna typografia i płynny ekran ładowania
- Bezpieczne API kontaktowe z limitowaniem żądań i wysyłką SMTP
- Przeglądarka struktury folderów projektu
Stos technologiczny
| Technologia | Wersja | Cel | Dlaczego wybrano |
|---|---|---|---|
| Next.js | ^16.1.6 | App Router framework | Server Components, file-based routing, API routes, image optimization |
| React | ^19.2.4 | UI library | Server Components and concurrent rendering |
| TypeScript | ^5 | Type safety | Typed project content catches slug/data mismatches at compile time |
| Tailwind CSS | ^4 | Utility-first styling | CSS-first config with @theme/oklch tokens, no JS config file |
| Framer Motion | ^12 | Animations | Stagger/fade/hover primitives with useInView and useReducedMotion |
| @xyflow/react + dagre | ^12.11.5 / ^0.8.5 | Architecture diagrams | Data-driven interactive graphs with automatic layout |
| Nodemailer | ^7.0.11 | Contact email delivery | Simple Gmail SMTP transport from a single API route |
| @upstash/ratelimit + @vercel/kv | ^2.1.0 / ^3.0.0 | Distributed rate limiting | Shared sliding-window counter across serverless instances |
| Radix UI + shadcn/ui | primitives + copied source | Accessible UI primitives | Accessible tooltips/labels with full style control via copied components |
| Vercel | — | Hosting & analytics | Zero-config Next.js deploys, CDN, Web Analytics |
Architektura
App Router Pages
- Root layout (server): fonts, metadata, Providers, Navbar, Footer, hexagon background
- Home (server): composes Profile, Recent Projects (first 4), Techstack, About sections
- /projects (client): stagger-animated grid of all ProjectCards
- /projects/[slug] (server): joins projects[] + projectDetails[] by slug at request time
- /about, /contact (client) and styled not-found page
Component Layer
- components/projects/: Project, ProjectCard, ReactFlowDiagram, FolderTree, MermaidDiagram
- components/animation/: Framer Motion wrappers (stagger, fade-up, hover glow, border trail)
- components/pattern/: InteractiveHexagonBg (rAF-optimized SVG grid), CssPattern, AnimatedHero
- components/ui/: shadcn/ui primitives (Badge, Button, Input, Label, Textarea, Tooltip)
- components/terminal/: Terminal typing preview component
Data & API Layer
- lib/projects/*.ts: one file per project exporting ProjectType + ProjectDetailType
- lib/projects/index.ts: aggregates projects[] and projectDetails[] arrays
- lib/types.ts: TECH_ICONS registry, PROFILE_DATA, and all content type definitions
- POST /api/contact: server-side validation, rate limiting, Nodemailer → Gmail SMTP
Struktura projektu
app
about
, app
contact
api
contact
projects
[slug]
components
animation
navbar
, components
footer
, components
profile
, components
theme
pattern
projects
terminal
ui
lib
projects
types.ts
utils.ts
public
Punkty końcowe API
Portfolio API (port 3000)
| Metoda | Trasa | Cel |
|---|---|---|
| POST | /api/contact | Validate contact form input, rate-limit by IP, send email via Gmail SMTP |
Kluczowe decyzje projektowe
Static TypeScript Data Instead of CMS
Decyzja: Store all project content as typed constants in lib/projects/*.ts joined by slug
Dlaczego: Type safety, zero runtime fetch cost, no database or CMS dependency
Korzyści: Compile-time checks, ships with bundle, server-renderable, free hosting footprint
Kompromisy: Content changes require code changes and redeployment
Server/Client Component Split
Decyzja: Detail pages and layout are server components; lists, diagrams, and forms are client components
Dlaczego: Minimize client JS while keeping interactive features
Korzyści: Smaller bundle, faster first paint, SEO-friendly detail pages
Kompromisy: Mental overhead of the serialization boundary
Tailwind CSS v4 CSS-First Config
Decyzja: Configure theme via @theme directives in globals.css instead of tailwind.config.js
Dlaczego: Tailwind v4 removes the JS config in favor of CSS-native tokens
Korzyści: One file for design tokens, oklch dark/light variables, simpler setup
Kompromisy: Different from v3 muscle memory
React Flow + Dagre for Diagrams
Decyzja: Derive architecture diagrams from data (nodes/edges) with Dagre auto-layout
Dlaczego: Diagrams stay consistent with content and render interactively
Korzyści: No hand-drawn images, zoom/pan, themable, ER table nodes supported
Kompromisy: Client bundle cost on pages that render diagrams
Layered Contact API Protection
Decyzja: Validate + HTML-escape inputs, then rate-limit via Upstash sliding window with in-memory fallback
Dlaczego: Serverless instances don't share memory; shared KV store gives consistent limits
Korzyści: XSS-safe output, 5 req/min/IP abuse protection, graceful degradation
Kompromisy: Requires KV env vars for full protection; no CSRF token yet
Gmail SMTP via Nodemailer
Decyzja: Send contact emails through an existing Gmail account
Dlaczego: Simplest delivery path for a personal portfolio with no backend infra
Korzyści: One route handler, no third-party email SaaS
Kompromisy: App password rotation, self-email only, SMTP rate limits
Testy
None configured•0 testów jednostkowych
Co jest testowane
Brakujące pokrycie
- Unit tests for contact API validation and escapeHtml()
- Unit tests for slug join logic between projects[] and projectDetails[]
- Component tests for ProjectCard and detail page sections
- E2E tests for contact form and project navigation flows
- CI pipeline with lint, typecheck, and build gates (GitHub Actions)
Kluczowe wyzwania
- Serverless rate limiting — in-memory Map resets on cold start; solved with optional Upstash KV sliding window
- Server/client component boundary — keeping detail pages as server components while diagrams and forms stay interactive
- Self-referential content — documenting the portfolio inside the portfolio without circular confusion
- Theme consistency across SVG icons, React Flow diagrams, and hexagon background in dark/light modes
- Static data still feeling dynamic — staggering animations and hover states over data-driven cards
Kluczowe wnioski
- Typed static data as a lightweight alternative to a CMS for content-heavy portfolios
- App Router server component split reduces client bundle while preserving interactivity
- Dagre layout with React Flow renders clean architecture diagrams from pure data
- Defense-in-depth for contact forms: validation, HTML escaping, and layered rate limiting
- CSS-first Tailwind v4 configuration with oklch tokens simplifies theming