🚧 Shadow Page — Under Construction

NJOY Website Redesign

Project status, milestones, and roadmap for the NJOY Restored Health & Aesthetics website redesign and ProspyrMed integration.

Overall Progress54%

15 of 28 milestones completed

Project Goals

Modern, responsive website with improved UX and performance
Native booking integration with ProspyrMed API (no external redirects)
Content management system for services, blog posts, and settings without code changes
Personalized quiz system that routes users to relevant services
E-commerce path — Finix hosted checkout for cart, memberships, and related flows (go-live pending env on preprod)
Full booking flow from service selection to appointment confirmation

ProspyrMed Connection Testing

Connection Works

Successfully connected to ProspyrMed. Can read providers, locations, and available appointment times.

Booking Form Built

Users can select provider, location, date, and time. Form validates all information before submitting.

Patient Creation Testing

Workspace ID received from ProspyrMed (42db00dd-ac4b-43eb-888e-7a95afb0ed93). Code and .env.example updated — next: controlled test on your deploy (still creates real data unless you use a test account).

Full Booking Test

After patient create succeeds, run the full flow (service → time → info → confirm appointment). Cancel or clean up test appointments in ProspyrMed if needed.

Demo Available: Visit /demo/booking to see the booking form in action and test what currently works.

What We've Built & Learned

Technical Setup

Built website using modern web framework (Next.js)
Set up database to store services, blog posts, and settings
Created admin dashboard so content can be updated without coding
Pre-production deploys via Docker on VPS (`npm run deploy:preprod`); local dev on `localhost:3000`
Payments: Finix hosted checkout on-site (Stripe SDK removed from codebase)

ProspyrMed Integration

Connected website to ProspyrMed booking system
Fixed connection issues to match how ProspyrMed actually works
Tested reading data: providers, locations, and available appointment times all work
Built booking form that lets users pick provider, location, date, and time
Workspace ID received and wired; patient-create + full booking still need controlled tests on deploy
Created demo page to show what works and what is still pending

User Experience

Booking happens on our website (users never leave to book)
Step-by-step booking form that guides users through the process
Shows real available appointment times from ProspyrMed
Quiz system that recommends services based on user answers
Admin can update content, services, and settings without a developer

Testing & Quality

Tested reading data from ProspyrMed (providers, locations, times)
Created demo page to show booking flow works up to final step
Tested booking form on different screen sizes
Verified all pages load quickly
Checked website works in different browsers

Current Blockers

ProspyrMed Workspace ID

resolved

Received from ProspyrMed: `42db00dd-ac4b-43eb-888e-7a95afb0ed93`. Set `PROSPYRMED_WORKSPACE_ID` in host env if you override defaults; run controlled patient-create + booking test on preprod.

Impact: Unblocked for integration testing — execution on deploy still pendingOwner: Michael / deployRequested: 2025-03-18

Finix preprod activation

in progress

Populate all `FINIX_*` variables and feature flags on VPS `/var/www/njoy/.env.production`, redeploy, then run sandbox checkout + webhook reconciliation (see `deploy/IMPLEMENTATION_TRACKER_2026-03-24.md`).

Impact: Online cart and membership checkout stay disabled or test-only until env is liveOwner: Michael / deployRequested: 2026-03-24

Test Account for Booking

pending response

Asked ProspyrMed if they have a separate test account we can use to practice booking appointments without creating real appointments in the system.

Impact: Limited ability to test the full booking process without affecting real patient dataOwner: ProspyrMed SupportRequested: 2025-03-18

Booking Form Field Requirements

waiting

Need confirmation from ProspyrMed on exactly what information is required when creating a patient and booking an appointment.

Impact: May need to adjust the booking form fields once we get confirmationOwner: ProspyrMed SupportRequested: 2025-03-18

Development Phases

Foundation & Setup

completed

Initial setup, architecture decisions, and core infrastructure

2024-12-01 → 2025-01-15

Milestones:

Next.js project setup with TypeScript
Completed: 2024-12-05
Supabase integration and schema design
Completed: 2024-12-10
Design system and component library
Completed: 2024-12-20
Deployment pipeline (VPS + Docker)
Completed: 2025-01-10

Core Features

completed

Essential website features and content management

2025-01-15 → 2025-02-28

Milestones:

Service pages with dynamic routing
Completed: 2025-01-25
Admin dashboard for content management
Completed: 2025-02-05
Quiz system with routing matrix
Completed: 2025-02-15
Membership and product catalog
Completed: 2025-02-25

ProspyrMed Integration

in progress

Connecting the website to ProspyrMed for booking appointments

2025-03-01 → 2025-03-31

Milestones:

Set up connection to ProspyrMed system
Completed: 2025-03-10
Match NJOY services to ProspyrMed services
Completed: 2025-03-15
Test reading data (providers, locations, available times)
Completed: 2025-03-18
Build booking form and user flow
Completed: 2025-03-18
Test creating a patient in ProspyrMed
⚠️ Workspace ID is configured (`42db00dd-ac4b-43eb-888e-7a95afb0ed93`). Next: controlled patient-create on preprod/staging (prefer test account when available).
Test booking an appointment
⚠️ After patient create succeeds on deploy, run `bookExternalAppointment` end-to-end and verify in ProspyrMed.
Test full booking flow end-to-end

Payments & Checkout (Finix)

in progress

Website commerce uses Finix hosted checkout (products, memberships, gift paths). In-clinic payments remain via ProspyrMed / Finix POS.

2025-03-15 → 2026-04-15

Milestones:

Replace Stripe with Finix hosted checkout + webhooks
Completed: 2026-03-25
Lead routing unified (Lead vs Opportunity) across form APIs
Completed: 2026-03-25
Homepage hero / nav spacing, safe-area, logo visibility
Completed: 2026-03-25
Finix credentials on preprod + sandbox E2E (cart → paid → order)
⚠️ Set `FINIX_*` on VPS `.env.production`, redeploy, then validate checkout URLs and webhook reconciliation (see deploy/IMPLEMENTATION_TRACKER).

Testing & Refinement

pending

Testing everything works, fixing issues, and making final improvements

2025-04-01 → 2025-04-15

Milestones:

Test booking flow with real ProspyrMed connection
Test website on different browsers (Chrome, Safari, Firefox)
Test on mobile phones and tablets
Check page load speeds and optimize if needed
Review and fix any SEO issues

Launch Preparation

pending

Final checks, documentation, and go-live

2025-04-15 → 2025-04-30

Milestones:

Production environment setup
Domain migration and DNS
Analytics and monitoring
Launch checklist completion

Last updated: April 1, 2026

← Back to site

Project Goals

Modern, responsive website with improved UX and performance
Native booking integration with ProspyrMed API (no external redirects)
Content management system for services, blog posts, and settings without code changes
Personalized quiz system that routes users to relevant services
E-commerce path — Finix hosted checkout for cart, memberships, and related flows (go-live pending env on preprod)
Full booking flow from service selection to appointment confirmation

ProspyrMed Connection Testing

Connection Works

Successfully connected to ProspyrMed. Can read providers, locations, and available appointment times.

Booking Form Built

Users can select provider, location, date, and time. Form validates all information before submitting.

Patient Creation Testing

Full Booking Test

After patient create succeeds, run the full flow (service → time → info → confirm appointment). Cancel or clean up test appointments in ProspyrMed if needed.

Demo Available: Visit /demo/booking to see the booking form in action and test what currently works.

What We've Built & Learned

Technical Setup

Built website using modern web framework (Next.js)
Set up database to store services, blog posts, and settings
Created admin dashboard so content can be updated without coding
Pre-production deploys via Docker on VPS (`npm run deploy:preprod`); local dev on `localhost:3000`
Payments: Finix hosted checkout on-site (Stripe SDK removed from codebase)

ProspyrMed Integration

Connected website to ProspyrMed booking system
Fixed connection issues to match how ProspyrMed actually works
Tested reading data: providers, locations, and available appointment times all work
Built booking form that lets users pick provider, location, date, and time
Workspace ID received and wired; patient-create + full booking still need controlled tests on deploy
Created demo page to show what works and what is still pending

User Experience

Booking happens on our website (users never leave to book)
Step-by-step booking form that guides users through the process
Shows real available appointment times from ProspyrMed
Quiz system that recommends services based on user answers
Admin can update content, services, and settings without a developer

Testing & Quality

Tested reading data from ProspyrMed (providers, locations, times)
Created demo page to show booking flow works up to final step
Tested booking form on different screen sizes
Verified all pages load quickly
Checked website works in different browsers

Current Blockers

ProspyrMed Workspace ID

resolved

Received from ProspyrMed: `42db00dd-ac4b-43eb-888e-7a95afb0ed93`. Set `PROSPYRMED_WORKSPACE_ID` in host env if you override defaults; run controlled patient-create + booking test on preprod.

Impact: Unblocked for integration testing — execution on deploy still pendingOwner: Michael / deployRequested: 2025-03-18

Finix preprod activation

in progress

Impact: Online cart and membership checkout stay disabled or test-only until env is liveOwner: Michael / deployRequested: 2026-03-24

Test Account for Booking

pending response

Asked ProspyrMed if they have a separate test account we can use to practice booking appointments without creating real appointments in the system.

Impact: Limited ability to test the full booking process without affecting real patient dataOwner: ProspyrMed SupportRequested: 2025-03-18

Booking Form Field Requirements

waiting

Need confirmation from ProspyrMed on exactly what information is required when creating a patient and booking an appointment.

Impact: May need to adjust the booking form fields once we get confirmationOwner: ProspyrMed SupportRequested: 2025-03-18

Development Phases

Foundation & Setup

completed

Initial setup, architecture decisions, and core infrastructure

2024-12-01 → 2025-01-15

Milestones:

Next.js project setup with TypeScript
Completed: 2024-12-05
Supabase integration and schema design
Completed: 2024-12-10
Design system and component library
Completed: 2024-12-20
Deployment pipeline (VPS + Docker)
Completed: 2025-01-10

Core Features

completed

Essential website features and content management

2025-01-15 → 2025-02-28

Milestones:

Service pages with dynamic routing
Completed: 2025-01-25
Admin dashboard for content management
Completed: 2025-02-05
Quiz system with routing matrix
Completed: 2025-02-15
Membership and product catalog
Completed: 2025-02-25

ProspyrMed Integration

in progress

Connecting the website to ProspyrMed for booking appointments

2025-03-01 → 2025-03-31

Milestones:

Set up connection to ProspyrMed system
Completed: 2025-03-10
Match NJOY services to ProspyrMed services
Completed: 2025-03-15
Test reading data (providers, locations, available times)
Completed: 2025-03-18
Build booking form and user flow
Completed: 2025-03-18
Test creating a patient in ProspyrMed
⚠️ Workspace ID is configured (`42db00dd-ac4b-43eb-888e-7a95afb0ed93`). Next: controlled patient-create on preprod/staging (prefer test account when available).
Test booking an appointment
⚠️ After patient create succeeds on deploy, run `bookExternalAppointment` end-to-end and verify in ProspyrMed.
Test full booking flow end-to-end

Payments & Checkout (Finix)

in progress

Website commerce uses Finix hosted checkout (products, memberships, gift paths). In-clinic payments remain via ProspyrMed / Finix POS.

2025-03-15 → 2026-04-15

Milestones:

Replace Stripe with Finix hosted checkout + webhooks
Completed: 2026-03-25
Lead routing unified (Lead vs Opportunity) across form APIs
Completed: 2026-03-25
Homepage hero / nav spacing, safe-area, logo visibility
Completed: 2026-03-25
Finix credentials on preprod + sandbox E2E (cart → paid → order)
⚠️ Set `FINIX_*` on VPS `.env.production`, redeploy, then validate checkout URLs and webhook reconciliation (see deploy/IMPLEMENTATION_TRACKER).

Testing & Refinement

pending

Testing everything works, fixing issues, and making final improvements

2025-04-01 → 2025-04-15

Milestones:

Test booking flow with real ProspyrMed connection
Test website on different browsers (Chrome, Safari, Firefox)
Test on mobile phones and tablets
Check page load speeds and optimize if needed
Review and fix any SEO issues

Launch Preparation

pending

Final checks, documentation, and go-live

2025-04-15 → 2025-04-30

Milestones:

Production environment setup
Domain migration and DNS
Analytics and monitoring
Launch checklist completion