golamrabbi696/clipchopper

1. Purpose and Deployment Shape

ClipChopper is a video-editing agency platform: public lead/booking acquisition, client production portal, admin operations, invoicing/payments, and support. It is a decoupled Astro frontend plus Laravel REST API, with generated frontend assets deployed under the backend public root for shared-hosting use.

• frontend/src/pages/index.astro

• backend/routes/api.php

• backend/public/install.php

2. Entry Points and Runtimes

Astro 5 provides static/SPA pages for public, client, invoice, and admin experiences. Laravel 11 is the API and server-side workflow runtime; its HTTP entry is public/index.php, CLI entry is Artisan, and scheduled reminders are a console command.

• frontend/src/pages/dashboard.astro

• backend/public/index.php

• backend/artisan

• backend/app/Console/Commands/SendBookingsReminders.php

3. API, Authentication, and Access Boundaries

routes/api.php is the main contract boundary between frontend and backend. JWT bearer authentication separates public routes from client portal routes; admin and superadmin middleware further restrict operational and platform-administration endpoints. Controllers are grouped by public, client, and admin concerns.

• backend/routes/api.php

• backend/app/Http/Middleware/AdminMiddleware.php

• backend/app/Http/Middleware/SuperAdminMiddleware.php

4. Booking-to-Client Production Flow

Public booking submission validates input, persists bookings, and can create client accounts. Booking status changes, meeting-link assignment, completion, and due reminders publish domain events that drive notifications. Bookings, users, leads, reminders, invoices, and deliverables form the central production record set.

• backend/app/Http/Controllers/PublicBookingController.php

• backend/app/Models/Booking.php

• backend/app/Events/BookingSubmitted.php

• backend/app/Listeners/SendBookingSubmittedMail.php

5. Client Portal and Operational Workflows

The client dashboard aggregates sessions, invoices, deliverables, profile data, and ticket conversations. Admin controllers manage the same production lifecycle: client accounts, bookings, deliverable uploads/feedback, invoice creation, and ticket status/replies. This is an API-driven portal rather than server-rendered Laravel UI.

• backend/app/Http/Controllers/Client/DashboardController.php

• backend/app/Http/Controllers/TicketController.php

• backend/app/Http/Controllers/Admin/DeliverableController.php

• backend/app/Models/ContentDeliverable.php

6. Payments, Mail, and External Notifications

Stripe Checkout is used for public invoice payment and webhook-driven payment processing. Configurable SMTP and templates support transactional mail; events/listeners encapsulate booking lifecycle delivery. Optional webhook settings and notifier service provide Discord/Telegram-style operational notifications.

• backend/app/Http/Controllers/StripeController.php

• backend/app/Services/DynamicMailerService.php

• backend/app/Services/WebhookNotifier.php

• backend/app/Models/Invoice.php

7. Persistence, Storage, and Administration

Eloquent models map a relational MySQL/MariaDB/SQLite schema, including Laravel cache/jobs tables. Public storage serves avatars and uploaded assets; private storage is reserved separately. Superadmin operations include backup/restore, cache/storage management, mail settings, and audit/email logs.

• backend/database/migrations/0001_01_01_000002_create_jobs_table.php

• backend/app/Http/Controllers/Admin/BackupController.php

• backend/app/Http/Controllers/Admin/MailSettingController.php

• backend/storage/app/private/.gitignore