## 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. 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: campaign site using Next.js
- Where can I host Pediatric dentistry: Campaign site built with Next.js?
- I need a genuinely specialized campaign site 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 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 pediatric dentistry workflow.

### Next Actions
- **Browse the catalog index**  
  - **Operation ID**: catalog_index
  - **Method**: GET
  - **Relative Path**: /v1/catalog

- **Search published recipes by intent, stack and constraints**  
  - **Operation ID**: search_recipes
  - **Method**: POST
  - **Relative Path**: /v1/catalog/search
  - **Parameters**: 
    - Query: Pediatric dentistry: campaign site using Next.js

- **Prepare a side-effect-free deployment plan for an authorized project**  
  - **Operation ID**: plan_deployment
  - **Method**: POST
  - **Relative Path**: /v1/catalog/plan
  - **Parameters**: 
    - Recipe ID: page:blueprints:pediatric-dentistry:campaign-site:next-js

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