Endodontics: campaign site using Next.js · Ample Computer

Endodontics: Campaign Site Using Next.js

A campaign site blueprint for endodontics built with Next.js on Ample. Domain schema:

Public information: procedure catalog, referral guidance for general dentists, specialist profiles and technology, locations. Kept out of scope until handling is reviewed: referral letters with patient identity, imaging files, clinical notes. Referral documents carry patient identity; keep them out of these workflows until handling is reviewed. Technical basis verified on Next.js: 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 endodontics domain.
    Create the tables procedures, referral_guides, locations, endodontists, asset_versions. Root canal and retreatment procedures live in procedures; keep the sensitive classes (referral letters with patient identity, imaging files, clinical notes) 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 endodontics workflow.
   $ ample logs <deployment_id> --kind build

How It Was Checked

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

Evidence

  1. November 5, 2026 · canary run
    Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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 Endodontics schema and workflow below build on that verified basis.

Tested Examples

What It Doesn’t Cover