# Oral surgery: company website using Django

## Overview
A company website blueprint for oral surgery built with Django on Ample. This blueprint outlines the structure and requirements necessary for creating a company website tailored for oral surgery practices. It includes:
- **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.

## Query Examples
- **Oral surgery: company website using Django**
- **Where can I host oral surgery: Company website built with Django?**
- **I need a genuinely specialized company website workflow covering public procedure-category content and referral-contact directory; no clinical referrals.**

## Technical Basis
The technical implementation uses Django, featuring a versioned, immutable-cached asset uploaded to a published bucket and served from a CDN URL alongside the app's public HTTPS URL.

## Resource Requirements
- **Primitive Requirements**:
  - Compute
  - CDN

## Workflow Steps
1. **Model the oral surgery domain**: Create tables for various components including procedures and instructions.
2. **Workflow step 1**: Model the public catalog and create tables for it.
3. **Workflow step 2**: Build the site and publish versioned static assets to the CDN bucket.
4. **Workflow step 3**: Ensure all sensitive data classes are kept out of the site, linking instead to separate systems.
5. **Workflow step 4**: Deploy and verify both the public URL and the CDN asset URL.

## Prerequisites
- A Django project set up with the required packages.
- Bucket credentials for public asset storage.
- A review of which oral surgery data classes may be handled within the public schema.

## Limitations
- No compliance is claimed as surgical and medication records are considered health data. Only public guidance is included here until actual data-handling requirements are reviewed.

## Examples
- Overview of a verified public web service basis for this blueprint is provided in: `tests/deploy-canaries/django-patterns`.

## Success Checks
- The app must respond on its public URL as expected.
- Validate the versioned-static-assets self-test based on provided examples.