## Cosmetic dentistry: company website using Next.js

### Summary
A company website blueprint for cosmetic dentistry built with Next.js on Ample. Domain schema: treatments (code, name, description, session_count, price_from): whitening, veneers, bonding and aligner offerings; before_after_galleries (treatment_id, title, consent_reference, published): consented, de-identified case galleries; locations (name, address, phone, opening_hours): practice locations; financing_options (name, provider, terms_summary): payment plans presented publicly; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: treatment catalog with session counts, consented case galleries, financing options, locations and hours. Kept out of scope until handling is reviewed: patient photographs without documented consent, clinical records, payment details. Case photographs are patient data; publish only with documented consent and de-identification. No health-data 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
- Cosmetic dentistry: company website using Next.js
- Where can I host Cosmetic dentistry: Company website built with Next.js?
- I need a genuinely specialized company website workflow covering public service-gallery content and approval workflow for published media; no patient files.

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

### Framework
Next.js

### Workload
Company website

### Industry
Cosmetic dentistry

### Release Status
Published

### Execution Status
Ready

### Workflow Steps
1. **Model the cosmetic dentistry domain**: Create the tables treatments, before_after_galleries, locations, financing_options, asset_versions. Whitening, veneers, bonding and aligner offerings lives in treatments; keep the sensitive classes (patient photographs without documented consent, clinical records, payment details) out of this schema.
2. **Model the public catalog as tables and render pages from them.**
3. **Build the site and publish versioned static assets to the CDN bucket.**
4. **Keep every sensitive data class out of the site; link to separate, authorized systems instead.**
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.**

### Examples
- **Next.js pattern fixture**: Verified public web service basis for this blueprint.

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

### Limitations
- The cosmetic dentistry schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No compliance claims are made. Case photographs are patient data; publish only with documented consent and de-identification.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 5.0
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

### Next Actions
- **Browse the catalog index**
- **Search published recipes by intent, stack and constraints**
- **Prepare a side-effect-free deployment plan for an authorized project**
- **Browse Cosmetic dentistry**
- **Browse Company website**
- **Browse Next.js**
- **Browse Deploy web app**