Project Summary
What this project currently includes
The project is now split into a public-facing side and an internal admin side. Public users are guided into a booking flow, while admins use a separate demo login to access the internal dashboard. This keeps the operational dashboard out of the public customer journey.
✓Completed / Available in Demo
- Commercial public website page
- Public booking page for studio, equipment, podcast and content bookings
- Internal dashboard prototype for admin use only
- Demo admin login page
- Favicon and basic branding applied across the pages
✕Still Outstanding
- Real database and backend logic
- Real payment integration
- Real user authentication and secure admin access
- Automatic handoff from public booking into admin records
- Live stock/availability logic for real equipment inventory
Feature Checklist
User-friendly status view
| Feature | Status | Notes |
|---|---|---|
| Can the public view the main website? | ✓ Yes | The commercial website is available as a branded public landing page. |
| Can the public open a booking page? | ✓ Yes | The public booking page is separate from the internal admin dashboard. |
| Can the public choose a studio booking? | ✓ Yes | Users can select a studio-style booking path and configure add-ons. |
| Can the public view equipment options? | ✓ Yes | The booking flow includes an equipment catalogue with visible rates and quantity selection. |
| Can the public see a live booking tally? | ✓ Yes | The page tallies session cost, extras, fees and an estimated deposit. |
| Can the public agree to terms before payment? | ✓ Yes | The payment step is gated behind a terms-and-conditions checkbox in the demo flow. |
| Can the public make a real payment? | ✕ No | The payment button is currently a demo placeholder and is not connected to a payment gateway. |
| Can admin log in? | ✓ Yes | A demo-only login page exists for presentations and internal demos, and the credentials can be shared privately when needed. |
| Can admin access the dashboard directly without login? | ✕ No | The dashboard now redirects to the demo login page unless the demo session is active. |
| Can admin log out? | ✓ Yes | A logout button clears the demo session and returns to the login page. |
| Do public bookings automatically appear inside the admin dashboard? | ✕ No | This still needs a backend or storage layer. The public and admin sides are not yet connected live. |
| Is the admin dashboard production-secure? | ✕ No | The current login is for demo purposes only and should not be treated as real security. |
Admin Capabilities
What admin can do now, and what admin should be able to do next
✓Admin demo features available now
- Log in through the demo admin login page
- Open the internal dashboard prototype
- View the dashboard, calendar, bookings, payments and equipment sections in the internal UI
- Log out of the demo session
- Use the internal interface for walkthroughs and stakeholder review
✕Admin features still required for full build
- Create real bookings from public submissions
- Add, edit and archive inventory items in a live database
- Approve or reject bookings
- Mark equipment as booked out, returned, damaged or unavailable
- Track payment status properly against each booking
- Send customer notifications automatically from the system
Admin access is available for demo walkthroughs, but the credentials are intentionally kept off this document and should be shared privately.
Booking Rules
Operational rules the final system must enforce
| Rule | Status | Meaning |
|---|---|---|
| No double-booking of studio slots | ✕ Not yet enforced | Once a studio session is confirmed for a date and time, another user should not be able to book the same slot. |
| No double-booking of equipment | ✕ Not yet enforced | If a camera or other item is booked out for a period, it must stop appearing as available for overlapping bookings. |
| Inventory availability must update automatically | ✕ Not yet enforced | Once equipment is reserved, the system should reduce available quantity or block that item until return. |
| Terms and conditions before payment | ✓ Demo flow exists | The public booking flow already requires the user to agree to terms before moving into the payment step. |
| Payment only after booking summary | ✓ Demo flow exists | The user sees their selected booking, add-ons and estimated deposit before being allowed to continue. |
| Notifications and reminders | ✕ Not yet implemented | The final system should send reminders such as “camera is due back on this date” and “your photoshoot is scheduled for this day”. |
Pages Delivered
What each page is for
✓Public Website
- Main marketing/commercial page for Focus Media
- Introduces the brand, services and booking call-to-actions
- Designed to direct customers into the public booking flow
✓Public Booking Flow
- Lets users choose a booking type
- Supports studio add-ons and equipment selection
- Shows summary, terms and demo payment handoff
✓Admin Login
- Demo-only gate before the internal dashboard
- Separates the public side from the internal side
- Useful for presentations and stakeholder review
✓Admin Dashboard
- Internal dashboard for bookings, calendar, payments and equipment
- Protected by demo session check
- Still a front-end prototype, not a live connected system
✓Inventory Upload Page
- Simple internal page for adding new inventory items in demo form
- Represents the planned admin flow for new gear entry
- Still not connected to a live database yet
Important Notes
Demo limitations and next steps
✕Not yet production-ready
- No real server-side booking submission
- No real admin user management
- No real Stripe/Paystack/Peach Payments integration yet
- No real email or WhatsApp automation yet
- No live inventory availability control yet
- No automatic notification workflow yet
✓Ready for demo and stakeholder review
- Explains the intended system flow clearly
- Lets users understand the public versus internal split
- Shows how bookings, tally, terms and payment should work
- Shows how admin access should look in a simple demo environment
Recommended next build phase:
connect the public booking flow to a backend, save submissions, push them into admin records, and replace the demo payment and demo login with real secure production integrations.
Requirements From George
What is needed from the client to complete the full system
| Required Item | Why it is needed |
|---|---|
| Verified WhatsApp Business number with Meta | Needed for proper customer notifications, booking reminders, due-back alerts and automated communication. |
| Online payment gateway account | Needed to take deposits or full payments online. Example options could include Paystack, Peach Payments or another preferred provider. |
| Full inventory list | Needed so each camera, light, mic, backdrop and accessory can be entered, priced and tracked correctly. |
| Inventory pricing and replacement values | Needed to calculate hire cost and define liability/damage rules for rented equipment. |
| Terms and conditions wording | Needed for cancellation rules, deposits, late returns, damage, overtime and other legal/operational policies. |
| Notification wording | Needed for message templates such as booking confirmation, payment received, shoot reminder and equipment due-back alerts. |
Contact