Corny Clouds
Corny Clouds is a Next.js platform for independent artists, cultural events, portfolio work, merchandise, and audience relationships. It brings expressive, brand-led public discovery together with customer accounts, commerce, and Sanity-powered studio operations.
Role
Full-stack Developer
Association
Niyalo Creatives
01
The context
The problem, people, and outcome in view.
The project needed to avoid becoming a generic merchandise store. Artists, events, cultural portfolio work, and product discovery needed to feel like connected parts of one identity, while editors and staff needed an operational path for maintaining artists, events, merchandise, and audience content.
02
The contribution
A clear view of what I owned.
Full-stack Developer
Responsibilities
Showing 10 of 31- Artist
- event
- portfolio
- and merchandise discovery experiences that connect public storytelling with the next appropriate customer action.
- CMS-backed artists
- event records
- event settings
- portfolio work
- products
- and editorial content through Sanity.
Capabilities applied
03
The work
From decisions to the working product.
Process
Yumesh owned approximately 80% of the full-stack implementation after taking over the project: the core frontend, backend workflows, CMS implementation, commerce, account flows, and continuous product refinement.
Satish Bajagain contributed in the early phase, including event-space and dashboard design work, a loading screen, sound effects, and selected animation work. Public credit: https://github.com/BajagainSatish
Solution
Artist, event, portfolio, and merchandise discovery experiences that connect public storytelling with the next appropriate customer action. CMS-backed artists, event records, event settings, portfolio work, products, and editorial content through Sanity. Event-detail flows for date, location, status, lineup, gallery, FAQ, sharing, ticket links, and related merchandise. Commerce with cart, persistent wishlist behavior, server-side product checks, Stripe payment intents, order verification, and customer order records. Authentication and protected customer/studio workflows using NextAuth and role-aware dashboard access. Brand-led light/dark themes, motion that responds to capability/reduced-motion constraints, loading treatment, and optional sound interactions. Error monitoring and test tooling.
04
The result
Proof over promises.
The source demonstrates payment-intent and order-verification code, not a verified live payment transaction. The case study must not claim live revenue, ticket sales, or audience outcomes without user-provided evidence.
05
Build notes
The tools and details that carried it through.
Technology
Showing 10 of 16Selected product details
- Artist, event, portfolio, and merchandise discovery experiences that connect public storytelling with the next appropriate customer action.
- CMS-backed artists, event records, event settings, portfolio work, products, and editorial content through Sanity.
- Event-detail flows for date, location, status, lineup, gallery, FAQ, sharing, ticket links, and related merchandise.
- Commerce with cart, persistent wishlist behavior, server-side product checks, Stripe payment intents, order verification, and customer order records.
- Authentication and protected customer/studio workflows using NextAuth and role-aware dashboard access.
- Brand-led light/dark themes, motion that responds to capability/reduced-motion constraints, loading treatment, and optional sound interactions.
- Error monitoring and test tooling.
Explore further
06
Connected work
Proof and writing from this project.
Project proof
Showing 5 of 16Frontend / Next.js
Corny Clouds: Next.js application architecture
Built an App Router application spanning public discovery, customer accounts, commerce, and studio surfaces. The route structure keeps those different product areas connected within one platform.
Frontend / State Management & Local Persistence
Corny Clouds: React state management
Implemented cart and wishlist state that persists locally and can synchronize with authenticated Sanity records. This lets guest browsing remain useful while supporting continuity after sign-in.
Frontend / TypeScript
Corny Clouds: TypeScript domain modelling
Modelled artists, events, portfolio entries, products, customers, and orders as typed application concepts. These contracts make the connections between creative content and commerce data explicit in the codebase.
CMS / Sanity CMS
Corny Clouds: Sanity CMS modelling
Modelled artists, events, portfolio work, merchandise, and site settings in Sanity. Editors can update those structured records without requiring a code change for routine publishing.
Soft Skills / Information Architecture
Corny Clouds: Creative information architecture
Connected artists, events, portfolio work, and merchandise through deliberate public navigation paths. Visitors can move between related creative content instead of encountering each section as an isolated page.
Works / 02 of 08