Back to Works
Works / 02Company

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

Timeline

Corny Clouds logo
Project evidence / 0216:10 view

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

  • 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.

Capabilities applied

Next.jsInteraction, Theme & Motion DesignCommerce & Inventory DataPayments, Webhooks & IntegrationsAuthentication & AuthorizationState Management & Local PersistenceSentry & ClarityTypeScriptSanity CMSInformation ArchitectureUX Workflow DesignResponsive UI Engineering

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

React state managementTypeScript domain modellingCreative information architectureEvent experience designResponsive frontend engineeringTheme systemsMotion-aware interactionAudio interaction integrationE-commerce workflowsStripe payment handlingAuthentication and authorizationWishlist synchronizationTransactional communicationError monitoring and qualitySanity CMS modellingNext.js application architecture

Selected 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

Frontend / Next.js

Corny Clouds: Next.js application architecture

Built an App Router application with connected public discovery, customer, commerce, and studio surfaces.

Corny CloudsFrontend

Frontend / State Management & Local Persistence

Corny Clouds: React state management

Implemented cart and wishlist state with local persistence and authenticated Sanity synchronization.

Corny CloudsFrontend

Frontend / TypeScript

Corny Clouds: TypeScript domain modelling

Modelled artists, events, portfolio work, products, customers, orders, and event metadata as typed application concepts.

Corny CloudsData

CMS / Sanity CMS

Corny Clouds: Sanity CMS modelling

Structured content so editors can manage artists, events, portfolio work, merchandise, and page settings without code changes.

Corny CloudsCMS

Soft Skills / Information Architecture

Corny Clouds: Creative information architecture

Connected artist, event, portfolio, and merchandise discovery into deliberate public journeys.

Corny CloudsProduct Delivery

Soft Skills / UX Workflow Design

Corny Clouds: Event experience design

Built event-detail pages with status, lineup, gallery, FAQ, sharing, ticket, and merchandise paths.

Corny CloudsProduct Delivery

Frontend / Responsive UI Engineering

Corny Clouds: Responsive frontend engineering

Implemented adaptable public and commerce interfaces across device sizes.

Corny CloudsFrontend

Frontend / Interaction, Theme & Motion Design

Corny Clouds: Theme systems

Added light/dark presentation without flattening the project’s expressive visual identity.

Corny CloudsFrontend

Frontend / Interaction, Theme & Motion Design

Corny Clouds: Motion-aware interaction

Used motion capability and reduced-motion-aware behavior to keep visual effects optional.

Corny CloudsFrontend

Frontend / Interaction, Theme & Motion Design

Corny Clouds: Audio interaction integration

Integrated optional sound effects into interactions while preserving core usability.

Corny CloudsProduct Delivery

Database / Commerce & Inventory Data

Corny Clouds: E-commerce workflows

Built product discovery, cart, checkout, order confirmation, and order visibility flows.

Corny CloudsProduct Delivery

Backend / Payments, Webhooks & Integrations

Corny Clouds: Stripe payment handling

Created and verified payment intents before recording order data.

Corny CloudsBackend

Backend / Authentication & Authorization

Corny Clouds: Authentication and authorization

Implemented NextAuth customer access and protected dashboard sessions.

Corny CloudsBackend

Frontend / State Management & Local Persistence

Corny Clouds: Wishlist synchronization

Merged guest wishlist state with authenticated Sanity-backed records.

Corny CloudsProduct Delivery

Backend / Payments, Webhooks & Integrations

Corny Clouds: Transactional communication

Implemented email-capable communication routes and contact handling.

Corny CloudsProduct Delivery

Tools / Sentry & Clarity

Corny Clouds: Error monitoring and quality

Configured monitoring and test tooling for a production-oriented Next.js codebase.

Corny CloudsQuality

Works / 02 of 08

Have a similar problem to solve? Let's talk.