JK
>読み込み中 // 読み込み中
ビューを初期化中
Completednextjsreacttypescripttailwind
Jitin K ポートフォリオ
マイクロサービス、分散システム、洗練されたフロントエンド技術を発信するフルスタックエンジニアポートフォリオ。
課題と解決策
豊かなアニメーション、完全な多言語対応、優れたCore Web Vitalsを両立した最高品質のWebサイトを構築すること。
機能
- Next.js App Routerとnext-intlによる9言語対応
- React Flowによる動的システムアーキテクチャ図
- キネティックタイポグラフィと滑らかなプリローダー
- レート制限とSMTP送信を備えたセキュアなコンタクトAPI
- プロジェクト構造を閲覧できるフォルダツリービューア
技術スタック
| 技術 | バージョン | 目的 | 採用理由 |
|---|---|---|---|
| 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 |
アーキテクチャ
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
プロジェクト構成
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
APIエンドポイント
Portfolio API （ポート 3000）
| メソッド | ルート | 目的 |
|---|---|---|
| POST | /api/contact | Validate contact form input, rate-limit by IP, send email via Gmail SMTP |
主要な設計判断
Static TypeScript Data Instead of CMS
判断: Store all project content as typed constants in lib/projects/*.ts joined by slug
理由: Type safety, zero runtime fetch cost, no database or CMS dependency
利点: Compile-time checks, ships with bundle, server-renderable, free hosting footprint
トレードオフ: Content changes require code changes and redeployment
Server/Client Component Split
判断: Detail pages and layout are server components; lists, diagrams, and forms are client components
理由: Minimize client JS while keeping interactive features
利点: Smaller bundle, faster first paint, SEO-friendly detail pages
トレードオフ: Mental overhead of the serialization boundary
Tailwind CSS v4 CSS-First Config
判断: Configure theme via @theme directives in globals.css instead of tailwind.config.js
理由: Tailwind v4 removes the JS config in favor of CSS-native tokens
利点: One file for design tokens, oklch dark/light variables, simpler setup
トレードオフ: Different from v3 muscle memory
React Flow + Dagre for Diagrams
判断: Derive architecture diagrams from data (nodes/edges) with Dagre auto-layout
理由: Diagrams stay consistent with content and render interactively
利点: No hand-drawn images, zoom/pan, themable, ER table nodes supported
トレードオフ: Client bundle cost on pages that render diagrams
Layered Contact API Protection
判断: Validate + HTML-escape inputs, then rate-limit via Upstash sliding window with in-memory fallback
理由: Serverless instances don't share memory; shared KV store gives consistent limits
利点: XSS-safe output, 5 req/min/IP abuse protection, graceful degradation
トレードオフ: Requires KV env vars for full protection; no CSRF token yet
Gmail SMTP via Nodemailer
判断: Send contact emails through an existing Gmail account
理由: Simplest delivery path for a personal portfolio with no backend infra
利点: One route handler, no third-party email SaaS
トレードオフ: App password rotation, self-email only, SMTP rate limits
テスト
None configured•ユニットテスト 0 件
テスト内容
不足しているカバレッジ
- 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)
主な課題
- ダークモードと多言語切り替え時のハイドレーション不一致の完全解消
- アクセシビリティ（動作軽減設定）に配慮したモーション制御
学んだこと
- Next.js App Routerにおける最新のi18n設計手法
- Vercel推奨のパフォーマンス最適化ベストプラクティス