## 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_months): braces and aligner options;
- **treatment_stages** (appliance_type_id, stage_no, 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_versions** (version, cdn_key, 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. No compliance is claimed.

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.

### Representative Queries
- Orthodontics: campaign site using Next.js
- Where can I host Orthodontics: Campaign site built with Next.js?
- I need a genuinely specialized campaign site workflow covering public specialty-service navigation and clinician information; no treatment records.

### Parent IDs
- industry:orthodontics
- workload:campaign-site
- stack:framework-next-js
- intent:deploy-web-app

### Resource Requirements
- primitive:compute
- primitive:cdn

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

### Workflow Steps
1. **Model the orthodontics domain**: Create the tables appliance_types, treatment_stages, locations, age_groups, asset_versions. Braces and aligner options live in appliance_types; keep sensitive classes (patient scans and treatment plans, progress photos, guardian and minor identity) 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.
7. **Verify**: Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the orthodontics workflow.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 5.0
- **Components**:
  - app server size: s-1vcpu-1gb, quantity: 1.0

### Limitations
- **Compliance**: No health, financial, privacy, or other compliance claim is made. Orthodontic plans and progress imagery are health data.
- **Public content**: Verified on the node-22 template at s-1vcpu-1gb; other sizes are unknown or unverified.

### Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search recipes by intent, stack and constraints**: POST /v1/catalog/search
- **Prepare a side-effect-free deployment plan for an authorized project**: POST /v1/catalog/plan
- **Read the existing agent authentication setup**: GET /mcp/setup
- **Browse Orthodontics**: GET /v1/catalog/nodes/industry%3Aorthodontics
- **Browse Campaign site**: GET /v1/catalog/nodes/workload%3Acampaign-site
- **Browse Next.js**: GET /v1/catalog/nodes/stack%3Aframework-next-js
- **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app