## Cosmetic dentistry: company website using Django

### Summary
A company website blueprint for cosmetic dentistry built with Django 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 includes:
- treatment catalog with session counts,
- consented case galleries,
- financing options,
- locations and hours.

### 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 live in treatments; keep sensitive classes 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.

7. **Verify**  
    Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the cosmetic dentistry workflow.

### Examples
- **Django 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 technical basis (public web service on Django) was verified with the pattern fixture; the cosmetic 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. Case photographs are patient data; publish only with documented consent and de-identification. No health-data compliance is claimed.

### 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
1. **Browse the catalog index**
2. **Search published recipes by intent, stack and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**
4. **Read the existing agent authentication setup**
5. **Browse Cosmetic dentistry**
6. **Browse Company website**
7. **Browse Django**
8. **Browse Deploy web app**

---

Preserve sensitive data handling practices when publishing or using patient information.