Nkosi Felix, Senior Data Platform Engineer

Enterprise Deliverables

Two shipped products, end to end.

Both were taken from a blank repo to a live, public production site: architecture, build, compliance-aware content, and the business-facing decisions behind them. Screenshots below are the real, live sites.

RetailVitamin — Independent D2C Commerce Build

Owner-operated direct-to-consumer supplement storefront. Designed, built, and shipped independently — architecture, storefront, and compliance-aware product content all in one build.

RetailVitamin storefront homepage: 'Build your daily stack with RetailVitamin' hero with a storefront photo

What I built

  • Shopify storefront + a companion Next.js app on Vercel for previewing cart and purchase-flow UI changes before they go live (interface preview only -- no real payment processing)
  • GitHub Actions governance layer: deterministic quality gates, a commit-message policy check, dependency updates (Dependabot), and repo-hygiene checks run on every change
  • A scoped "remote hotfix" pipeline: a narrow, allowlisted set of theme files can be patched through a validated, receipt-generating pipeline with an explicit human confirmation step before anything is pushed to production
  • Theme preview and production deploy workflows kept separate, each with its own validation pass before a push is allowed

Product & business design

  • Compliance-aware supplement copy standard: no disease-treatment claims, no FDA-approval language, no unsupported health-outcome promises
  • Trust-first storefront layout: a Certificate of Analysis for every current SKU, published GMP facility documentation, and a clearly stated 30-day return policy up front
  • Positioning built around transparency ("build your daily stack") rather than supplement-industry hype language
RetailVitamin daily ritual and trust section from the live storefront
RetailVitamin product grid and shop sections from the live storefront

Boundary: Public storefront and public compliance/trust copy only. No customer, order, or payment data is shown or referenced.

Feel Easy Around Travel — Client Engagement

A group-travel planning business, built for a paying client who owns and operates the brand. Shown here with the client's approval.

Feel Easy Around Travel homepage: 'Luxury-feeling group trips, handled from strategy to delivery' hero

What I built

  • A Next.js site on Vercel with a public marketing/booking surface and a separate owner-login area for the business operator
  • A "Strategy Session" booking flow that converts a group-trip inquiry into a scoped engagement, rather than a generic contact form
  • Per-trip group guide pages that automatically retire after the trip's access period ends, instead of staying live indefinitely as stale content

Product & business design

  • Positioning written around removing planning stress for couples and friend groups booking Caribbean and Mexico trips, not around the technology behind it
  • A structured "strategy to delivery" service model: destination direction, itinerary planning, and group coordination presented as one clear path instead of an open-ended consulting offer
  • Destination catalog scoped to a specific, defensible set of Caribbean and Mexico locations rather than an unbounded "anywhere" promise

Boundary: Client account systems, pricing, and private trip details are not shown. This describes the engineering and product-design work only, with the client's approval to reference the public site by name.