Capability
6 content types, published through 1 studio
E-Commerce
Heartful Revolution
A platform for independent artists to manage six kinds of public content from one screen, built on a payment processor suited to its actual African-market-oriented user base.
MusicE-CommercePaymentsCreator PlatformContent Management
Visit live siteHeartful Revolution
The Challenge
Independent artists needed to manage six different kinds of public content — tracks, merch, magazine pieces, lectures, events, and blog posts — without needing six separate publishing tools, while the platform itself needed a payment processor suited to its actual (African-market-oriented) user base rather than a default choice.
The Solution
A single Creator Studio composes six independently-built form components (TrackForm, ProductForm, MagazineForm, LectureForm, EventForm, BlogForm) behind one tabbed interface, each rendered conditionally based on the active tab — so a creator manages their entire public output from one screen, while each content type still gets a form purpose-built for its own fields (audio + lyrics for tracks; venue + date for events).
The Engineering
Next.js with a full Paystack integration spanning three server routes — initialize (start a transaction), verify (confirm after redirect), and webhook (async payment confirmation) — the standard three-part pattern for a redirect-based payment gateway, plus a separate PaystackDonationCard component supporting donation flows distinct from commerce checkout.
One Creator Studio, six content forms
Creator Studio
tabbed interface
TrackForm
ProductForm
MagazineForm
LectureForm
EventForm
BlogForm
Paystack payment cycle
Initialize
start transaction
→
Verify
confirm after redirect
→
Webhook
async payment confirmation
Built For
CreatorsFans & CustomersAdministrators
The System
Cart and the multi-page auth flow were consolidated into fewer screens during the platform's generalization from its original devotional framing to a secular indie-music identity — a content and narrative rewrite (the Mission page, nav labels like "Vaishnava Songs") layered on top of unchanged commerce and creator infrastructure, proving the underlying architecture was decoupled from the specific content domain it originally served.
Homepage
Music / track browsing
Artist profile
Shop / product page
Creator Studio
Creator sales & analytics
The Outcome
Six content types are published through one interface instead of six, without collapsing their forms into a single generic "add content" form that would lose type-specific fields. Payment confirmation runs through a proper initialize/verify/webhook cycle rather than trusting client-side redirect state alone. The platform's entire content domain was changed (devotional → secular) with zero changes required to the commerce or creator-publishing code underneath it — direct evidence the two layers were properly separated.
Reliability
Init / verify / webhook payment cycle
Architecture
0 commerce changes on a full content-domain rewrite
Technologies
Next.jsPaystackWebhooks
Have a system like this in mind?
Let's scope the architecture and plan the build.