CASE STUDY
Eden of the West: Building a Music Platform That Grows With Its Community
IMPACT
10+ years of continuous operation and community growth
A music streaming radio station platform combining chill music with anime culture. A decade-long evolution from WordPress to modern, scalable web application.
TIMELINE
10+ years (ongoing)
ROLE
Co-founder and full-stack engineer
TEAM
Started with a group of friends sharing a passion for chill music and nerd culture
THE CHALLENGE
The original WordPress setup could not handle growing listener demand and needed modernization to keep pace with technological advances while maintaining the community's core values.
THE RESULTS
- Nearly 10 years of continuous operation
- Growing passionate listener community
- Platform serves as a learning laboratory for emerging technologies
- Ongoing infrastructure migration to keep streaming resilient
THE SOLUTION
Progressive technology migration—transitioned from WordPress to Laravel, implemented AzuraCast (PHP-based with a Vue frontend), and continued evolving toward Nuxt 3 with serverless and microservice patterns. Real-world listener usage guides each architecture step without chasing vanity metrics.
TECHNOLOGIES USED
- Nuxt 3
- Vue.js
- Node.js
- Serverless
- Microservices
- JAMstack
- Azuracast
Project Details
What problem does Eden of the West keep solving?
Eden of the West is an internet radio station that mixes chill music with anime culture. Co-founded with friends, it has stayed online for over a decade because the product and the community grew together. The original WordPress stack stopped being a good fit for streaming demand and modern delivery expectations.
How has the stack evolved over ten-plus years?
The path has been progressive, not a single rewrite: WordPress, then Laravel, then AzuraCast for station operations, with continued work toward Nuxt 3, serverless, and microservice pieces. The site remains a living lab—new patterns get tested against real listening habits instead of speculative rewrites.
What does the current infrastructure migration involve?
Homelab operations now center on AzuraCast and a host migration between staging and production station servers. Station media, database, and metrics volumes are treated as first-class migration units, with restore verification before media moves. That work is about keeping the station online and maintainable—not inventing listener-count claims.
Why keep building without fabricated growth metrics?
Listener passion and featured artists are the motivation, but measurable audience KPIs are not claimed here. Success is framed as continuity, community stewardship, and infrastructure that can absorb the next decade of changes.
MORE WORK
OTHER CASE STUDIES
TrustClarity: Buyer Portal Rebuild — Search-First TC 2.0 Platform
IMPACT:
400+ Storybook stories across 130+ components (from 11), WCAG 2.1 AA remediation, RFQ flow with server-side credential fix, and 1,533 lines of storefront code removed for a search-first pivot
React/Next.js rebuild of TrustClarity's core buyer workflows — Figma-to-production, WCAG 2.1 AA, Storybook/Chromatic visual gates, and a search-first architecture that replaced the per-org storefront layer.
TrustClarity: Orchestrating Google Jules Multi-Agent Delivery on the Buyer Platform
IMPACT:
Four signed merges into develop covering AGENTS.md plus three UAT fixes; one additional thumbnail/search fix with a TypeScript no-suppression governance lesson; durable signed-commit / pull-and-re-PR playbook confirmed across later Jules rounds
Production orchestration of Google Jules on the TrustClarity buyer platform — first and second UAT rounds, signed-commit re-PR playbook, prompt discipline, and AGENTS.md governance that kept parallel cloud sessions safe to merge.
TrustClarity: Supply-Chain Security Analysis and CI/CD Hardening
IMPACT:
14 of 20 repositories remediated before TrustClarity production; 3 attack vectors eradicated; SHA-pinned reusable security-scan workflow rolled out to 20 repos; later SHA-pin and merge-base invisibility controls shipped
Org-wide supply-chain security analysis for TrustClarity — malicious code found in 14 of 20 repositories across three attack vectors, remediated in repos before it reached TrustClarity's own production environment, followed by a SHA-pinned reusable CI/CD security pipeline and later hardening controls.