drawleados-dotcom/drawleadweb

Purpose and runtime

This is a PHP website/CMS for Drawlead: public marketing, service/industry/platform pages, blogs and case studies, plus interactive booking, WhatsApp, SEO analysis, and popup features. It is designed for an Apache-style PHP deployment, indicated by .htaccess, PHP entry files, and deployment workflow. Persistent content and feature state are database-backed through SQL schema/migrations.

Key runtime roots: index.php, includes/bootstrap.php, .htaccess.

Public site composition and routing

index.php is the public entry point and likely resolves requested pages/content before assembling shared layout and page-specific bodies. Templates separate reusable page chrome from content types, enabling database-managed pages alongside dedicated templates.

Architecture boundary: request/bootstrap → page/content selection → layout partials → rendered HTML.

Key paths: index.php, templates/layout-start.php, templates/layout-end.php.

Template and content model

The public presentation layer has explicit templates for homepage variants, blog lists/posts, case studies, booking, service solutions, industries, and platform modules. Shared navigation, footer, sidebar, popup, booking modal, and WhatsApp widget are independently composable partials.

This supports a hybrid content model: fixed template types populated by CMS/database records, rather than a single static-site build.

Key paths: templates/home-body.php, templates/blog-post-body.php, templates/partials/nav.php.

Administration CMS

The /admin application is the control plane for authentication, users, pages, blogs, case studies, calendar/booking configuration, WhatsApp flows, popups, analytics, and deployments. Edit/delete endpoints imply server-rendered CRUD workflows backed by the shared database and admin-specific assets.

The admin boundary should enforce authentication/session handling before accessing content or operational actions.

Key paths: admin/index.php, admin/login.php, admin/page-edit.php.

Interactive lead-capture APIs

Public JavaScript calls PHP API endpoints for booking availability/slots/submission and WhatsApp flow/submission. Browser widgets are decoupled from server endpoints, allowing the public templates to embed lead-capture experiences without exposing administration interfaces.

Primary flow: public widget → assets/*.js → /api endpoint → database and likely outbound notification/email.

Key paths: api/booking-submit.php, api/whatsapp-flow.php, assets/booking.js.

Shared application services

includes/bootstrap.php is the likely shared initialization boundary for configuration, database connectivity, sessions, and common helpers. The application also contains a mailer integration and an analysis feature with dedicated templates and admin support, making these cross-cutting services rather than isolated pages.

Key paths: includes/bootstrap.php, includes/mailer.php, includes/analyze.php.

Database evolution and operational state

The SQL schema establishes the baseline data model; ordered migrations add booking, WhatsApp bots, case studies/services, SEO fields, popups/triggers, service/platform/industry pages, page status/menu behavior, and analysis features. admin/run-migrations.php provides an in-application migration operation, so production migration access is an important operational/security boundary.

Key paths: sql/schema.sql, sql/migrations/003_booking_system.sql, admin/run-migrations.php.

Deployment and infrastructure

Deployment is automated through GitHub Actions, with repository deployment instructions available separately. Apache configuration is repository-managed via root and upload-directory .htaccess files; uploads are persistent application data and need writable storage plus access-control review.

Key paths: .github/workflows/deploy.yml, DEPLOYMENT.md, uploads/.htaccess.