## Pediatric Dentistry: Knowledge Base using Next.js

A knowledge base 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. 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
- Pediatric dentistry: knowledge base using Next.js  
- Where can I host Pediatric dentistry: Knowledge base built with Next.js?  
- I need a genuinely specialized knowledge base workflow covering public age-group content navigation and caregiver-facing information; no child records.

### 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.

### Prerequisites
1. A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)  
2. Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)  
3. A review of which pediatric dentistry data classes may be handled at all; this blueprint models public information only

### Workflow 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. Model articles and categories as tables keyed to the public catalog entities.
3. Build the site with versioned assets served from the CDN bucket.
4. Keep articles free of any sensitive data class.
5. Deploy and verify the public URL and the CDN asset URL.
6. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.  
   Command: `ample deploy . --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. Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the pediatric dentistry workflow.  
   Command: `ample logs  --kind build`

### 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.
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

### Cost Estimate
- **Monthly Amount:** 5.0 USD  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- Components:  
  - App server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0  
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Evidence Summary
- **Kind:** canary_run  
  - **Summary:** Next.js pattern fixture deployed on Ample; 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.
- **Observed At:** 2026-09-21T02:34:39Z  
- **Implementation Revision:** 1d28ae0-dirty (CLI 0.1.21)  
- **Expires At:** 2027-03-20T02:34:39Z  
- **Scope:** checks: [`/p/versioned-static-assets`], pattern: `pattern:public-web-service`, template: `node-22`

### Formats
- **HTML:** [https://ample.computer/blueprints/pediatric-dentistry/knowledge-base/next-js](/content/blueprints/pediatric-dentistry/knowledge-base/next-js/index.html)  
- **Markdown:** [https://ample.computer/blueprints/pediatric-dentistry/knowledge-base/next-js.md](/content/blueprints/pediatric-dentistry/knowledge-base/next-js.md)  
- **JSON:** [https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Apediatric-dentistry%3Aknowledge-base%3Anext-js](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Apediatric-dentistry%3Aknowledge-base%3Anext-js)