next js.md

Pediatric dentistry: campaign site using Next.js

Summary

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.

Infrastructure requirements

Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
CDN: verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.)

Prerequisites

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_*)

Exact tested configuration

template: node-22
runtime: node
size: s-1vcpu-1gb
install: npm install
build: npm run build --if-present
start: npm run start

Steps

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.
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 pediatric dentistry workflow.
```
ample logs <deployment_id> --kind build
```

Tested examples

Next.js pattern fixture (tests/deploy-canaries/next-js-patterns): Verified public web service basis for this blueprint.

Success checks

app responds on its public URL (/ on the live URL, expect ample canary next js patterns)
versioned-static-assets self-test from the example (/p/versioned-static-assets on the live URL, expect see the pattern fixture checks)

Limitations

The technical basis (public web service on Next.js) was verified with the pattern fixture; the pediatric dentistry schema and workflow are an original design for this blueprint and were not executed as a separate application.
No health, financial, privacy or other compliance claim is made. Data about minors is doubly sensitive; only public practice information belongs in these workflows. No compliance is claimed.
Public content and synthetic examples only until actual data-handling requirements have been reviewed.
Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

app server x1 s-1vcpu-1gb: 5.00 USD

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.