Photography studios: documentation site using Django · Ample Computer

Photography studios: documentation site using Django

A documentation site blueprint for photography studios built with Django on Ample. Domain schema: listings (reference, session_type, price_from, publishing_status, agency_id): session packages with publishing status; agencies (name, location, studio_count): studios or locations; galleries (listing_id, object_key, cdn_key, consent_reference): published portfolio media; reports (agency_id, period, object_key, generated_at): studio booking reports; state_transitions (record_type, from_state, to_state): the allowed state machine. Public information: session packages and pricing from, consented portfolio galleries, studio locations. Kept out of scope until handling is reviewed: client galleries before release, minors in photographs, payment details. Client galleries are private until released with consent; only consented portfolio media is public. Technical basis verified on Django: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the photography studios domain. Create the tables listings, agencies, galleries, reports, state_transitions. Session packages with publishing status lives in listings; keep the sensitive classes (client galleries before release, minors in photographs, payment details) out of this schema.

  2. Workflow step 1. Model versioned documents with a state machine (draft, review, published) scoped to a product version

  3. Workflow step 2. Publish assets for released versions to the CDN bucket

  4. Workflow step 3. Serve only published versions publicly

  5. Workflow step 4. Deploy and verify the version list and a published page

  6. Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

   $ ample deploy . --name <app-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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the photography studios workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

✓app responds on its public URL· http get/ → “ample canary django patterns”
✓relational-records self-test from the example· http get/p/relational-records → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template); the relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's Photography studios schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover