Proof point → Five years separate my first copy-pasted Express boilerplate from this codebase. The distance between them is the distance every growing team needs to travel - and I know every step of the road.

🩻 Problem

A producer brand selling beats and services needs what enterprises have - reliable tracking, fast pages, funnel discipline - at creator-economy budgets. Off-the-shelf tools leak data, double-count conversions, and fall over under ad traffic.

🔨 Solution

richiedagenius.com - brand presentation, beat discovery/buyer conversion, and lead capture as one platform:

Architecture Overview

  1. Modern edge stack - Next.js 16 + React 19 + Tailwind + Framer Motion, deployed to Cloudflare Workers via OpenNext, with Supabase (auth/SSR), Upstash rate limiting, and Sentry.
  2. Server-side tracking as a product - an event-ingestion API route with validation and deduplication, dispatching to six ad platforms’ conversion APIs (Meta, TikTok, Snap, X, Reddit, Pinterest), plus a Cloudflare Worker cron syncing Meta Ads data into Supabase.
  3. Config as source of truth - funnel stages, retargeting sequences, and the public surface live in validated JSON, enforced by 15 guardrail scripts (several with their own tests) run in CI.
  4. Operational knowledge, versioned - docs/ carries architecture, design-system, governance, and deployment guides plus a full ad-ops library: creative-testing framework, retargeting sequence system, funnel drop-off diagnosis.
  5. Campaign infrastructure - dedicated landing pages with funnel tests, a blog with view counting, tokenized lead-magnet downloads, and a health endpoint with Telegram alerting (tested).

Quality signals (verified, not claimed)

512 files, 89 test files, 188 commits over ~8 months. CI pipeline: validate public surface → lint → vitest → Next build → OpenNext build, with concurrency groups and frozen lockfiles; separate deploy and Supabase-keepalive workflows; pre-commit hooks with staged quick checks; LICENSE and NOTICE.

📜 Philosophy

Marketing infrastructure is software. Ad campaigns and retargeting windows are config under CI guardrails; tracking is server-side, deduplicated, and rate-limited; every public route ships with tests. Operational knowledge lives next to the code it operates.

🎓 Key learnings

  • Edge deployment economics and pain (OpenNext asset validation exists for a reason).
  • Privacy-conscious conversion tracking across six platforms - the post-cookie marketing stack, hand-built.
  • Config validation as a CI discipline - preventing the class of bug where the settings are wrong.
  • The five-year arc itself: the same author’s 2020 boilerplate is visible in this portfolio, and the delta is the curriculum.

📈 Output & impact

  • A live, deployed commercial property with verifiable engineering rigor - the endpoint (so far) of the portfolio’s maturity arc.

🌍 Why this matters

Platforms & Registries · Original Tools & IP. Public-facing platforms - commercial or civic - should run at this standard: tested, validated, edge-fast, observable, on a lean budget. And it is local IP: built in Lagos for a Nigerian creative business, exportable as method.

🚀 Hire me

Want your platform edge-fast, tested, and tracking truthfully? Let’s talk → · See also: MelodicJeanious · The thesis