## Pediatric dentistry: company website using Next.js

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

### Workflow Steps
1. **Model the pediatric dentistry domain**: Create the tables services, first_visit_guides, locations, providers, asset_versions. Age-appropriate services live 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 public catalog as tables and render pages from them.
3. **Workflow step 2**: Build the site and publish versioned static assets to the CDN bucket.
4. **Workflow step 3**: Keep every sensitive data class out of the site; link to separate, authorized systems instead.
5. **Workflow step 4**: Deploy and verify the public URL and the CDN asset URL.
6. **Deploy**: 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. **Verify**: 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`

### Success Checks
- App responds on its public URL
- Versioned-static-assets self-test from the example

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

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

### Next Actions
- [Browse the catalog index](/v1/catalog)
- [Search published recipes by intent, stack and constraints](/v1/catalog/search)
- [Prepare a side-effect-free deployment plan for an authorized project](/v1/catalog/plan)
- [Read the existing agent authentication setup](/mcp/setup)
- [Browse Pediatric dentistry](/v1/catalog/nodes/industry%3Apediatric-dentistry)
- [Browse Company website](/v1/catalog/nodes/workload%3Acompany-website)
- [Browse Next.js](/v1/catalog/nodes/stack%3Aframework-next-js)
- [Browse Deploy web app](/v1/catalog/nodes/intent%3Adeploy-web-app)