React/Next.js dev — build out a drag-and-drop wedding floor-plan editor

About us WeddingDayPlan is a live B2B SaaS that wedding coordinators use to run weddings end to end — guests, tasks, schedules, documents, and a seating & floor-plan studio. Next.js 14 (App Router), TypeScript, Tailwind, Supabase (Postgres + Auth + Storage + RLS), deployed on Vercel. Real product, paying tiers, clean codebase. The work Our seating tool is already strong: a to-scale canvas in metres or feet, real table sizes with chair envelopes, drag-and-drop down to the individual seat, dietary flags on every name, minimum-spacing and walkway rules, AI-assisted auto-seating, plan versions, venue-plan image underlay, and a venue-ready PDF export. Our benchmark is the seating tool at https://planning.wedding/seating-chart — have a proper play with it before applying. There are a handful of specific things it does that we don't, and closing that gap is the job. Starting point — one paid task Add walls, columns and dividers as first-class objects on the canvas: placeable, rotatable, resizable, enterable by typed measurement, respected by our existing collision and spacing rules, and drawn correctly in the PDF export. This is a real feature we want shipped, not a throwaway exercise — you'll be paid for it, and it's how we find out how we work together. If that goes well there's a clear queue of follow-on work on the same tool, plus other projects on the roadmap. You should have Strong React + TypeScript (hooks, performance, state that doesn't re-render the world) Real experience with interactive canvas / SVG / drag-and-drop geometry — collision, snapping, rotation, coordinate systems. This is the part people underestimate. Comfort working inside an existing codebase rather than starting fresh (the editor alone is ~6,000 lines and is heavily commented — read it, don't rewrite it) Next.js App Router and server actions Nice to have: Supabase / Postgres / RLS, jsPDF or similar To apply Answer the three questions below. Please skip the template cover letter — I read the answers, not the intro paragraph. A link to something spatial or interactive you've built (editor, map, diagram, planner, game) counts for more than a CV. Screening questions: (1) compare planning.wedding's tool to ours and say what you'd change first — you'll need to fill in your live URL, the repo only has localhost; (2) describe an interactive canvas/editor you've built and the hardest geometry or perf problem in it; (3) how do you make your first safe change in a 6,000-line inherited component.