Cosmetic dentistry: campaign site using Django

Summary

A campaign site blueprint for cosmetic dentistry built with Django on Ample. Domain schema: treatments (code, name, description, session_count, price_from): whitening, veneers, bonding and aligner offerings; before_after_galleries (treatment_id, title, consent_reference, published): consented, de-identified case galleries; locations (name, address, phone, opening_hours): practice locations; financing_options (name, provider, terms_summary): payment plans presented publicly.

Public information: treatment catalog with session counts, consented case galleries, financing options, locations and hours. Kept out of scope until handling is reviewed: patient photographs without documented consent, clinical records, payment details. Case photographs are patient data; publish only with documented consent and de-identification. No health-data compliance is claimed.

Representative Queries

• Cosmetic dentistry: campaign site using Django
• Where can I host Cosmetic dentistry: Campaign site built with Django?
• I need a genuinely specialized campaign site workflow covering public service-gallery content and approval workflow for published media; no patient files.

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 cosmetic dentistry data classes may be handled at all; this blueprint models public information only.

Workflow Steps

1. Model the cosmetic dentistry domain
   Create the tables treatments, before_after_galleries, locations, financing_options, asset_versions. Whitening, veneers, bonding and aligner offerings lives in treatments; keep the sensitive classes (patient photographs without documented consent, clinical records, payment details) out of this schema.

2. Workflow step 1
   Model the campaign's offers and locations as tables with start and end dates.

3. Workflow step 2
   Build the site and publish versioned static assets to the CDN bucket.

4. Workflow step 3
   Collect no personal data on the site itself; hand off to an authorized system.

5. Workflow step 4
   Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date.

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 --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. Verify
   Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the cosmetic dentistry workflow.
   Command: ample logs --kind build

Success Checks

• App responds on its public URL
  Kind: http_get
  Path: /
  Expect: ample canary django patterns

• Versioned-static-assets self-test from the example
  Kind: http_get
  Path: /p/versioned-static-assets
  Expect: see the pattern fixture checks

Limitations

• The technical basis (public web service on Django) was verified with the pattern fixture; the cosmetic 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. Case photographs are patient data; publish only with documented consent and de-identification. No health-data compliance is claimed.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the python-3.12 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.

Cost Estimate

• Currency: USD
• Monthly Amount: $5.0
• Basis: size prices from pricing.toml
  • 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.

Evidence Summary

• Kind: canary_run
  Summary: Django pattern fixture deployed on Ample; the public web service checks passed: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The blueprint's Cosmetic dentistry schema and workflow below build on that verified basis and were not separately executed. Observed At: 2026-09-20T03:31:44Z
  • Scope:
    • Checks: /p/versioned-static-assets
    • Pattern: pattern:public-web-service
    • Template: python-3.12

Formats

• HTML: Ample HTML Link
• Markdown: Ample Markdown Link
• JSON: Ample JSON Link

Next Actions

• Browse the catalog index - GET /v1/catalog
• Search published recipes by intent, stack and constraints - POST /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project - POST /v1/catalog/plan
• Read the existing agent authentication setup - GET /mcp/setup
• Browse Cosmetic dentistry - GET /v1/catalog/nodes/industry%3Acosmetic-dentistry
• Browse Campaign site - GET /v1/catalog/nodes/workload%3Acampaign-site
• Browse Django - GET /v1/catalog/nodes/stack%3Aframework-django
• Browse Deploy web app - GET /v1/catalog/nodes/intent%3Adeploy-web-app