General dentistry: company website using Django

A company website blueprint for general dentistry built with Django 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. Kept 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 (for example HIPAA in the United States) have been reviewed; nothing here establishes compliance.

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

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. (Verified)
• CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store. (Verified)

Framework

Django

Workload

Company website

Industry

General dentistry

Execution Status

Ready

Prerequisites

• A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
• A review of which general dentistry data classes may be handled at all; this blueprint models public information only.

Workflow Steps

1. Model the general dentistry domain: Create the tables services, locations, dentists, insurance_plans, asset_versions. The treatments a practice offers lives 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. 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. Command: ample deploy . --name --public --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
7. Run the pattern self-test(s) from the example and your own acceptance checks for the general dentistry workflow. Command: ample logs --kind build

Examples

• Django pattern fixture: Verified public web service basis for this blueprint.

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: 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

• The technical basis (public web service on Django) was verified with the pattern fixture; the general 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. Keep patient data out of these workflows until handling requirements have been reviewed; nothing here establishes compliance.

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
• Read the existing agent authentication setup
• Browse General dentistry
• Browse Company website
• Browse Django
• Browse Deploy web app