The CMS is the production source of truth
Live roster, release, event, and editorial updates flow through permissioned records so the team can operate without code changes.
Loading portfolio
Product and backend / Current
Kilogbede Records LTD
A growing label needs to publish artists, releases, editorial media, video, playlists, events, and campaigns quickly without losing brand coherence or requiring a developer for every update. The same platform must manage large media libraries, external music data, commerce links, permissions, and multiple domains.
I engineered the platform as a CMS-backed label operating surface rather than a static artist website. Public presentation is separated from content operations; structured records drive the roster, releases, music, events, posts, video, galleries, and connected commerce, while storage, public curation, administration, and audit remain distinct concerns.
- Role
- Product designer / Full-stack engineer
- For
- DZND LTD
- Stage
- Live in production
Walkthrough
Watch it run
Captured from the live public site: the label home, roster, catalogue and media, then the CMS model behind them.
My part
What I built
- Defined the information architecture, visual direction, interactions, and responsive composition.
- Built public experiences for artists, management, releases, music, video, editorial, events, galleries, and campaigns.
- Designed the content model and CMS workflows used by non-technical administrators.
- Implemented role-aware administration, audited actions, previews, and protected destructive operations.
- Built the media library around object storage, database metadata, folder indexing, curated albums, transforms, and synchronisation.
- Connected music, social, commerce, and event systems through bounded integrations with fallback states.
Decisions
The choices that shaped it
Storage and curation are different systems
Folders organise physical media; albums organise public storytelling. One asset can participate in multiple campaigns without copies or moves.
Media edits are metadata
Crop, focal position, transforms, poster, and playback choices remain reversible, protecting originals and supporting different contexts.
Operational tools are product work
Publishing, media sync, previews, audit, provisioning, and migration safety determine whether the public experience remains maintainable after launch.
What has been shown to work
- Ran type checking, linting, production builds, and strict preflight checks.
- Tested CMS create, edit, reorder, publish, preview, and fallback behaviour.
- Reviewed upload, transform, folder index, album curation, synchronisation, unlink, and protected deletion paths.
- Verified routing and metadata across the label, store, and admin domains.
- Tested music, social, event, commerce, and media integrations with unavailable and incomplete-content states.
Screens
From the product
Phone screens
At phone size
Technical detailOpen the system view
SYSTEM ARCHITECTURE
Multi-host music, media and commerce platform
A shared operational core powers a public label site, standalone store and administration surfaces while structured content, media storage, commerce and external music data remain separate concerns.Label, release, editorial and store journeys
Label, store and administration surfaces
Roster, releases, media, events and products
Neon Postgres and operational metadata
Cloudflare R2, folders and curated albums
Paystack, Spotify and event integration
- 01Audiencebrowse / buyFour hostnames
- 02Four hostnamespublished viewPurpose-built CMS
- 03Purpose-built CMSstructured recordsStructured state
- 04Purpose-built CMScuration metadataMedia layer
- 05Purpose-built CMSbounded integrationCommerce & music
Security and privacy
- Administrative writes are permission-checked and audit-oriented.
- Destructive media operations are separated from non-destructive curation.
- Credentials, payment configuration, artist operations, and unpublished media remain private.
Built with
Links
More work
eventOSA live ticketing and event operations platform covering public discovery, ticket sales, organiser tools, payouts, offline door scanning and a headless API that other websites use to sell tickets.Live in productionXcroTrustEngineered a four-surface escrow product across public web, consumer mobile, backend services, and operational administration, implementing a supplied design while keeping transaction outcomes and intervention paths server-controlled.Pre-launchNutrifluxA Nigerian-first nutrition mobile app and API combining deterministic health state, structured AI planning, offline-resilient writes, social features, reminders, observability and review-gated safety controls.Pre-launch