Technology Stack
This project intentionally uses modern, production-ready tools that reflect current industry standards.
Frontend Frameworkβ
Next.js 15β
- App Router architecture
- Server Components
- Optimized routing
- Built-in SEO capabilities
- Edge-ready deployment
Why Next.js?
It provides full-stack capabilities within a single framework, enabling API integration, server-side rendering, and optimized performance.
Styling Systemβ
Tailwind CSSβ
- Utility-first design
- Rapid UI development
- Consistent spacing system
- Clean design constraints
Why Tailwind?
It encourages systematic design and reduces CSS complexity.
UI Component Systemβ
shadcn/uiβ
- Accessible primitives
- Composable components
- Modern design patterns
- Built on Radix UI
Why shadcn?
It allows full control over components without locking into heavy UI frameworks.
Documentation Platformβ
Docusaurusβ
- Static site generation
- Versionable documentation
- MDX support
- Built-in search
- Clean sidebar navigation
Why Docusaurus?
It treats documentation as a first-class engineering artifact.
API Integrationβ
GitHub REST APIβ
- Repository data
- Stars
- Metadata
- Automated project listing
Why integrate GitHub?
- Keeps portfolio dynamic
- Eliminates manual project updates
- Demonstrates real API integration capability
Deploymentβ
Vercelβ
- CI/CD automation
- Preview deployments
- Edge infrastructure
- Zero-downtime builds
Why Vercel?
It integrates seamlessly with Next.js and supports independent deployments inside a monorepo.
Architectural Philosophyβ
The stack was chosen based on:
- Scalability
- Maintainability
- Developer experience
- Production-readiness
- Industry alignment
This project is not built as a static personal website.
It is built as a structured, extensible software system.