Endodontics: Company Website Using Django

Summary

A company website blueprint for endodontics built with Django on Ample.
Domain schema:

• procedures (code, name, description, typical_visits): root canal and retreatment procedures;
• referral_guides (procedure_id, referring_dentist_checklist, imaging_needed): public guidance for referring practices;
• locations (name, address, phone, opening_hours): clinic locations;
• endodontists (name, registration_number, technologies): specialists and equipment listed publicly;
• asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket.

Public Information

• Procedure catalog
• Referral guidance for general dentists
• Specialist profiles and technology
• Locations

Kept Out of Scope Until Handling is Reviewed

• Referral letters with patient identity
• Imaging files
• Clinical notes

Public Information Verification

No compliance is claimed.
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

• Endodontics: company website using Django
• Where can I host Endodontics: Company website built with Django?
• I need a genuinely specialized company website workflow covering public specialty pages and practice contact routing; no patient intake.

Workflow Steps

1. Model the endodontics domain: Create the tables procedures, referral_guides, locations, endodontists, asset_versions.
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.
7. Verify: Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the endodontics workflow.

Technical Configuration

Tested Configuration:

• Template: python-3.12
• Runtime: python
• Size: s-1vcpu-1gb
• Install: python3 -m pip install --target .ample/python -r requirements.txt
• Start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

Resource Requirements

• Compute
• CDN

Infrastructure Requirements

1. Compute:
   • Status: verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle.
2. CDN:
   • Status: verified
   • Summary: The CDN host serves objects from published buckets.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Basis: Size prices from pricing.toml at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

Limitations

• The technical basis was verified with the pattern fixture; the endodontics 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.
• Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits, and other sizes are unknown or unverified.

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 Endodontics
• Browse Company website
• Browse Django
• Browse Deploy web app