page:blueprints:pediatric dentistry:company website:django

Pediatric dentistry: company website using Django

Summary

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

• services (code, name, age_range, description): age-appropriate services
• first_visit_guides (age_range, checklist, what_parents_bring): public preparation guidance
• locations (name, address, phone, opening_hours, child_facilities): practice locations
• providers (name, registration_number, pediatric_certification): clinicians
• asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket.

Public information: services by age range, first-visit guidance, locations with child facilities, provider credentials. Kept out of scope until handling is reviewed: minor patient identity and guardians, clinical records, school and consent forms. Data about minors is doubly sensitive; only public practice information belongs in these workflows. No compliance is claimed.

Supporting Information

• Primary Queries:
  1. Pediatric dentistry: company website using Django
  2. Where can I host Pediatric dentistry: Company website built with Django?
  3. I need a genuinely specialized company website workflow covering public age-group content navigation and caregiver-facing information; no child records.

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

Workflow Steps

1. Model the pediatric dentistry domain: Create the tables services, first_visit_guides, locations, providers, asset_versions. Age-appropriate services live in services; keep the sensitive classes (minor patient identity and guardians, clinical records, school and consent forms) 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 pediatric dentistry workflow.

Limitations

• The technical basis (public web service on Django) was verified with the pattern fixture; the pediatric dentistry schema and workflow were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Data about minors is doubly sensitive; only public practice information belongs in these workflows. No compliance is claimed.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• 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.00
• 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.00
    • 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; 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.
• Observed At: 2026-09-20T03:31:44Z
• Last Verified At: 2026-09-20T03:31:44Z

Formats

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

Next Actions

• Action: Browse the catalog index
• Action: Search published recipes by intent, stack and constraints
• Action: Prepare a side-effect-free deployment plan for an authorized project
• Action: Read the existing agent authentication setup
• Action: Browse Pediatric dentistry
• Action: Browse Company website
• Action: Browse Django
• Action: Browse Deploy web app

Input Schema

• Properties:
  • env (array of encrypted environment variables, up to 50 items)
  • name (app name, regex: ^[a-z0-9-]+$)
  • path (project directory or ample.toml service)
  • release_command (migration command run before activation)
  • start (start command)

Example

Title: Django pattern fixture
Description: Verified public web service basis for this blueprint.
Source Ref: tests/deploy-canaries/django-patterns