A live-style project timeline for the Ahmed Ramah coaching platform, built from the current delivery plan and implementation roadmap.
Booking, pricing, and Kashier payment foundations are now in place. The practical next move is production setup, calendar, email, and final QA.
Premium public frontend, standalone backend, PostgreSQL database, admin auth, offerings, availability, free booking, quote requests, pricing, and paid booking foundation.
Kashier test mode is connected with iFrame checkout, signed callback handling, duplicate-payment safeguards, and backend reconciliation against Kashier order status.
Production HTTPS domain, live Kashier credentials, Google Calendar/Meet, email notifications, legal pages, deployment hardening, and final browser QA.
The payment flow now follows a production-grade pattern: one payment reference per booking, backend verification, and reconciliation with Kashier before confirming the booking.
The timeline keeps the client focused on sequence: admin and offerings first, then booking, payment, integrations, QA, and deployment.
MVP scope, product docs, architecture, requirements, and delivery boundaries are now structured.
Use the documentation pack as the operating reference for implementation.
The API service, database foundation, schema, health routes, auth, and offerings endpoints are in place.
Add audit logs, rate limiting, production logging, permissions, and executable API docs.
Create the protected operational area that the admin will use to manage the platform.
Navigation, session check refinement, and logout.
Make programs and services editable from admin and use them as booking source of truth.
Build create/edit form, category selector, pricing controls, and publish workflow.
Give admin control over site settings, navigation, pages, sections, legal pages, SEO, blog, and media.
Create CMS APIs and dense admin screens for content operations.
Build availability, slots, dynamic forms, free booking submission, and admin booking review.
Keep booking QA running while paid flow, calendar, and email integrations are finalized.
Add country-aware pricing, checkout sessions, payment confirmation, and production-safe payment safeguards.
Switch local callback/return URLs to production HTTPS, add live credentials, and run final paid booking QA on the live domain.
Create calendar events, generate Meet links, sync busy blocks, and expose failures to admin.
Finalize Google ownership model, implement event creation, cancellation, retry, and failure visibility.
Send booking, payment, admin, cancellation, and reschedule notifications with delivery records.
Select provider, create email adapter, templates API, delivery logs, and retry handling.
Keep the existing premium frontend while wiring offerings, booking, legal, loading, and error states.
Complete mobile/browser QA and final copy checks after production URLs are set.
Reduce launch risk across auth, booking, pricing, payment, admin, and public UX.
Add backend tests, frontend browser smoke tests, booking happy path tests, and payment return tests.
Prepare a reproducible production-like deployment with HTTPS, envs, backups, logs, and monitoring.
Finalize compose/proxy setup, configure backups, monitoring, migrations, and rollback notes.
Complete final content, production keys, legal pages, SEO, mobile QA, and launch sign-off.
Run final production checks after booking, payment, calendar, email, and admin workflows are complete.
These decisions can move in parallel with admin and offerings work, but they must be closed before paid booking, emails, calendar, and launch.