Building a Digital Twin Portfolio: From JSON to Production

# Building a Digital Twin Portfolio ## The Concept Most portfolios are static HTML pages that require manual updates across multiple files. I wanted something different—a **"Digital Twin"** architecture where a single JSON file serves as the source of truth for my entire professional identity. ## The Architecture ```typescript // Single source of truth public/data/master_report.json // Typed data layer lib/masterReport.ts lib/types.ts // Next.js App Router app/projects/[slug]/page.tsx app/experience/page.tsx ``` ## Key Benefits 1. **Single Update Point** - Change data once, update everywhere 2. **Type Safety** - Full TypeScript coverage 3. **Static Generation** - Blazing fast page loads 4. **API-Ready** - Expose data via clean endpoints ## Implementation Details The portfolio uses Next.js 16 with React 19, leveraging Server Components for zero client-side JavaScript on content pages. All project pages are statically generated at build time using `generateStaticParams`. ## Lessons Learned - Next.js 16 changed `params` to be a Promise (breaking change!) - JSON-LD structured data is crucial for AI discoverability - Dynamic sitemaps improve SEO significantly *This is a placeholder post. Full content coming soon!*