I’ve already wired up Framer for the front-end, Thenty for memberships, and a Supabase + Vercel stack that stores every onboarding submission. The pieces all talk to each other—until I try to surface the data on the user side. Here’s where I’m stuck: once someone finishes onboarding I want to drop them onto a private dashboard where they can review and edit their profile information, membership details, and every answer they gave in the onboarding form. Profile and membership bits load fine; the onboarding form data section shows nothing unless I hard-code a static API link. Each onboarding record is made up of custom fields, so a rigid schema isn’t an option. What I need from you • Diagnose why dynamic onboarding data isn’t hydrating in the dashboard (currently built in Framer, fetching from Supabase via API routes on Vercel). • Implement a clean, maintainable solution—whether that means patching the existing Framer/Thenty setup or migrating the front-end to a more scalable Next.js approach. • Automatically generate a public, SEO-friendly page for every user (e.g. /u/username) that pulls the same Supabase data and updates whenever the user edits their info. • Push working code and clear commit messages to my GitHub repo; no breaking changes to existing auth or payment flows. Acceptance criteria 1. After login, a test user sees live profile, membership, and onboarding data—no static links or console errors. 2. Editing any field persists to Supabase and reflects instantly on both the dashboard and the public page. 3. New users automatically receive a unique public URL at account creation. 4. The solution is documented in README: env vars, schema changes, and deployment steps for Vercel. Tech on the table: Supabase (Postgres), Vercel, Framer, Thenty. Comfortable with React/Next.js, Typescript, or whatever you deem best—as long as it scales. If this sounds straightforward to you, let’s talk and get the data flowing. I Have ac omplete document with prototype and more informations if needed