Content Platform
DJ Snowlion
A production Next.js content platform combining structured content management, PostgreSQL, YouTube API integration, video discovery, and scalable full-stack architecture.
01
Project Overview
DJ Snowlion is a production content platform designed around video discovery, creator content, structured editorial data, and a responsive user experience.
The application combines a Next.js frontend with Sanity-managed content, PostgreSQL-backed application data, YouTube API integration, and Vercel deployment while keeping each data source separated behind clear application boundaries.
The project was designed to support continued expansion into member functionality, authentication, user profiles, and other interactive features without requiring the core content architecture to be rebuilt.
02
Architecture
- Next.js App Router for application routing, layouts, server rendering, and frontend composition
- Sanity for structured editorial content and content-management workflows
- PostgreSQL for relational application data outside the CMS
- YouTube API integration for creator video discovery and external media data
- Dedicated data-access boundaries separating YouTube data, CMS content, and application persistence
- Vercel for production deployment, preview environments, and hosting
03
Engineering Decisions
- Separated CMS-managed editorial content from external YouTube data so each source can evolve independently
- Used modular application and UI components instead of concentrating page logic into large monolithic components
- Kept YouTube integration and data retrieval separate from presentation components
- Used PostgreSQL for application-owned relational data instead of forcing all application state into the CMS
- Designed the architecture so authentication, member profiles, and future community features can be added without restructuring the existing content system
- Kept deployment and production configuration compatible with Vercel-based development and preview workflows
04
Challenges
- Integrating remote YouTube data alongside site-managed editorial content without tightly coupling the two systems
- Keeping content discovery responsive while handling external API data and pagination
- Maintaining clear ownership boundaries between CMS content, relational application data, and third-party video data
- Designing the initial architecture so future authenticated member functionality can be introduced incrementally
05
Testing & Validation
- Production build validation before deployment
- ESLint and formatting validation
- Manual responsive testing across desktop, tablet, and mobile viewport sizes
- Production deployment verification through Vercel
- Validation of YouTube content retrieval, navigation, search, and video playback workflows
06
Technology Stack
Explore More
Interested in the Engineering Behind the Project?
View my professional background, explore the rest of my development work, or contact me for a technical discussion or private source review.