Pediatric dentistry: campaign site using Next.js · Ample Computer

Pediatric dentistry: campaign site using Next.js

a campaign site blueprint for pediatric dentistry built with Next.js on Ample. Domain schema: services (code, name, age_range, description): age-appropriate services; first_visit_guides (age_range, checklist, what_parents_bring): public preparation guidance; locations (name, address, phone, opening_hours, child_facilities): practice locations; providers (name, registration_number, pediatric_certification): clinicians; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: services by age range, first-visit guidance, locations with child facilities, provider credentials. Kept out of scope until handling is reviewed: minor patient identity and guardians, clinical records, school and consent forms. Data about minors is doubly sensitive; only public practice information belongs in these workflows. 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

build npm run build --if-present

install npm install

runtime node

sizes-1vcpu-1gb

start npm run start

template node-22

Steps

  1. Model the pediatric dentistry domain. Create the tables services, first_visit_guides, locations, providers, asset_versions. Age-appropriate services lives in services; keep the sensitive classes (minor patient identity and guardians, clinical records, school and consent forms) 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=...
    ```

7. **Verify.** Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the pediatric dentistry 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 Pediatric dentistry schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover