Orthodontics: campaign site using Laravel · Ample Computer

Orthodontics: campaign site using Laravel

A campaign site blueprint for orthodontics built with Laravel on Ample. Domain schema:

Public information: appliance options and durations, stage-by-stage expectations, age-group guidance, locations. Kept out of scope until handling is reviewed: patient scans and treatment plans, progress photos, guardian and minor identity. Orthodontic plans and progress imagery are health data; keep them out of scope until handling is reviewed. Technical basis verified on Laravel: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.

What it runs on

You need

Exact tested configuration

Steps

  1. Model the orthodontics domain. Create the tables appliance_types, treatment_stages, locations, age_groups, asset_versions. Braces and aligner options lives in appliance_types; keep the sensitive classes (patient scans and treatment plans, progress photos, guardian and minor identity) out of this schema.

  2. Workflow step 1. Model the campaign's offers and locations as tables with start and end dates.

  3. Workflow step 2. Build the site and publish versioned static assets to the CDN bucket.

  4. Workflow step 3. Collect no personal data on the site itself; hand off to an authorized system.

  5. Workflow step 4. Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date.

  6. Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

   $ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...  
  1. Verify. Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the orthodontics workflow.
   $ ample logs <deployment_id> --kind build  

How it was checked

✓ app responds on its public URL· http get/ → “ample canary laravel patterns”
✓ versioned-static-assets self-test from the example· http get/p/versioned-static-assets → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template); the public web service checks passed: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The blueprint's Orthodontics schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover