Phoenix Gamification Landing
Turn sessions into habits. Streaks, missions, leaderboards and rewards on top of the product an operator already has, with no engineering on their side.

gamification.phoenixverse.io is the landing page for Phoenix Gamification: streaks, missions, leaderboards and rewards that run on top of whatever product an operator already has. One integration, live loops, and the operator's own engineers never touch it.
Built during my time at Phoenix Games (Oct 2025 to Sep 2026). It is the one Phoenix site on a white sheet, and it looks nothing like its sisters on purpose. Gamification is the friendly product in the family, so the page is warm where the others are dark.
What is on the page
- A hero whose headline is hand-lettered artwork, not live type: fat orange letters with a cream halo, set on an empty white sheet, with faded medals and ribbons drifting behind it. The accent colour is a marker on the page, never a ground for text
- What you can run. The loops themselves: streaks, missions, leaderboards, rewards, with drawn level badges at LV 5, LV 12 and LV 30, two drawings of each
- The platform. How the loops read from the ledger and write back to the wallet, and where the operator sees them
- Implementation. How long it takes and who does what. The page says plainly where Phoenix stops and the operator starts, because an engagement product that overpromises gets switched off in month two
- A contact form redesigned from a two-column form on a grey sheet into something that belongs to the page
Why it reads differently
The first draft was a centred column on an empty sheet, which is the default every landing page falls into. The fix was to give the page one object with real presence, the lettered headline, and let everything else stay quiet around it. Each floating ball in the hero carries its own scroll trigger, so the page feels drawn rather than animated.
Engineering
- Vite, React 19, TypeScript, Tailwind v4
- Lenis smooth scroll with CSS-driven reveals. No GSAP on this page, because the page did not need it and the budget is tighter on a page whose hero is an image
- Self-hosted fonts, and the same build and deploy path as the rest of the family
- Published through the shared monorepo pipeline to Cloudflare Workers static assets, with a preview URL on every pull request
The hub it belongs to: Phoenix Verse.