Orthodontics: campaign site using Next.js · Ample Computer
Orthodontics: campaign site using Next.js
A campaign site blueprint for orthodontics built with Next.js on Ample. Domain schema:
appliance
types (code, name, description, typical
duration
types): braces and aligner options; treatment
tages (appliance
type
id, stage
o, name, what
to expect): public description of treatment phases; locations (name, address, phone, opening
hours): practice locations; age
groups (name, guidance): children, teens and adults guidance; asset
tversions (version, cdn
d, published
at): versioned assets served from the CDN bucket. 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 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
Computeverified
Apps run in isolated x86 to64 Firecracker microVMs; sizes are the priced VM sizes.CDNverified
A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.
You need
A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
Bucket credentials from
ample bucket createpassed as encrypted S3_
- environment variables and a published bucket for public assets (CDN_ *)
- A review of which orthodontics data classes may be handled at all; this blueprint models public information only
Exact tested configuration
build
npm run build --if-present
install
npm install
runtime
node
sizes-1vcpu-1gb
start
npm run start
template
node-22
Steps
Model the orthodontics domain. Create the tables appliance types, treatment tages, locations, age groups, asset tversions. 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.
Workflow step 1. Model the campaign's offers and locations as tables with start and end dates
Workflow step 2. Build the site and publish versioned static assets to the CDN bucket
Workflow step 3. Collect no personal data on the site itself; hand off to an authorized system
Workflow step 4. Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date
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=...
- 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 next js patterns”
✓versioned-static-assets self-test from the example· http get/p/versioned-static-assets → “see the pattern fixture checks”
Evidence
- 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 Orthodontics schema and workflow below build on that verified basis.
Tested examples
- Next.js pattern fixture. Verified public web service basis for this blueprint.
What it doesn’t cover
The technical basis (public web service on Next.js) was verified with the pattern fixture; the orthodontics schema and workflow are an original design for this blueprint, built on that basis.
Orthodontic plans and progress imagery are health data; keep them out of scope until handling is reviewed.
Verified on the node-22 template at s-1vcpu-1gb.
Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.