# General dentistry: campaign site using Next.js

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

- **services** (code, name, description, duration_minutes, price_from): the treatments a practice offers;
- **locations** (name, address, phone, opening_hours, accessibility_notes): each practice location;
- **dentists** (name, registration_number, specialties, location_id): the clinicians listed publicly;
- **insurance_plans** (name, accepted_at_location_id): plans accepted per location;
- **asset_versions** (version, cdn_key, published_at): versioned assets served from the CDN bucket.

Public information: service catalog with prices from, locations, hours and parking, clinician profiles and registrations, accepted insurance plans.

Kept out of scope until handling is reviewed: patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person. Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been reviewed.

## What it runs on

- **Compute:** Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- **CDN:** 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 create` passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
- A review of which general dentistry 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

1. **Model the general dentistry domain.** Create the tables services, locations, dentists, insurance_plans, asset_versions. The treatments a practice offers lives in services; keep the sensitive classes (patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person) 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.  
   ```sh  
   $ 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 general dentistry workflow.  
   ```sh  
   $ 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 General dentistry 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 general dentistry schema and workflow are an original design for this blueprint, built on that basis.
- Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been 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-url` returns presigned upload URLs.
