### Oral surgery: company website using Laravel

A company website blueprint for oral surgery built with Laravel on Ample.

**Domain schema:**  
- **procedures** (code, name, description, anesthesia_options, recovery_days): extractions, implants and corrective surgery;  
- **pre_op_instructions** (procedure_id, instructions, fasting_rules): public preparation guidance;  
- **post_op_instructions** (procedure_id, instructions, warning_signs): public recovery guidance;  
- **locations** (name, address, phone, opening_hours, emergency_line): surgery locations;  
- **asset_versions** (version, cdn_key, published_at): versioned assets served from the CDN bucket.

**Public information:** procedure catalog with recovery expectations, pre- and post-operative instructions, emergency contact per location.

Kept out of scope until handling is reviewed: surgical records and consent forms, medication lists, insurance pre-authorizations. Surgical and medication records are health data; only public guidance belongs here. No compliance is claimed.

**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
- Oral surgery: company website using Laravel  
- Where can I host Oral surgery: Company website built with Laravel?  
- I need a genuinely specialized company website workflow covering public procedure-category content and referral-contact directory; no clinical referrals.

### Workflow Steps
1. **Model the oral surgery domain:**  
Create the tables procedures, pre_op_instructions, post_op_instructions, locations, asset_versions. Extractions, implants and corrective surgery lives in procedures; keep the sensitive classes (surgical records and consent forms, medication lists, insurance pre-authorizations) 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 oral surgery workflow.

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

**Components:**  
- **app server:** size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0

**Note:** Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Limitations
- No health, financial, privacy or other compliance claim is made. Surgical and medication records are health data; only public guidance belongs here. No compliance is claimed.

- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.