## General dentistry: company website using Laravel

### Summary
A company website blueprint for general dentistry built with Laravel on Ample.

#### Domain schema:
- **services** (code, name, description, duration_minutes, price_from): the treatments a practice offers.
- **locations** (name, address, phone, opening_hours, accessibility_notes): each practice location.
- **dentists** (name, registration_number, specialties, location_id): the clinicians listed publicly.
- **insurance_plans** (name, accepted_at_location_id): plans accepted per location.
- **asset_versions** (version, cdn_key, published_at): versioned assets served from the CDN bucket.

### Public information:
- Service catalog with prices from, locations, hours and parking.
- Clinician profiles and registrations.
- Accepted insurance plans.

#### Out of scope until handling is reviewed:
- Patient identity and contact details.
- Clinical records, x-rays and treatment notes.
- Appointment history tied to a person.

Patient data is health data. Keep it out of these workflows until handling requirements have been reviewed; nothing here establishes compliance.

### Technical basis
Verified on Laravel: 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
- General dentistry: company website using Laravel
- Where can I host General dentistry: Company website built with Laravel?
- I need a genuinely specialized company website workflow covering public service catalog and location-specific information; no patient data.

### Workflow Steps
1. **Model the general dentistry domain**  
   Create the tables services, locations, dentists, insurance_plans, asset_versions. The treatments a practice offers live in services; keep the sensitive classes (patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person) 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 general dentistry workflow.  
   Command: `ample logs  --kind build`

### Examples
- **Laravel 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
- No health, financial, privacy or other compliance claim is made. Patient data is health data. Keep it out of these workflows until handling requirements have been reviewed; nothing here establishes compliance.  
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

### Cost Estimate
- **Monthly Amount:** $5.00  
- **Basis:** Size prices from pricing.toml (loaded by the API).

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