Creator businesses: documentation site using Django

Summary

A documentation site blueprint for creator businesses built with Django on Ample. Domain schema includes:

• customer_workspaces (name, membership_tier, joined_at): member accounts or communities.
• content_items (title, tier_required, object_key, published_at, version): versioned content releases.
• customer_assets (workspace_id, title, object_key, visibility): downloads granted to a member.
• releases (content_item_id, version, notes): release notes per version.
• state_transitions (record_type, from_state, to_state): the allowed state machine.

Public information includes free content and previews, membership tiers, and creator profiles. Private data like member identity and payment status are kept out of scope until handling is reviewed.

Representative Queries

• Creator businesses: documentation site using Django
• Where can I host Creator businesses: Documentation site built with Django?
• I need a genuinely specialized documentation site workflow covering sponsor/client workspaces, publication guides and content assets.

Resource Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs.
• Postgres: Managed PostgreSQL 16 runs in its own microVM when needed.
• CDN: The CDN host serves objects from published buckets.

Framework

• Django

Workload

• Documentation site

Prerequisites

1. A Django project installed with dependencies from requirements.txt.
2. A PostgreSQL driver reading DATABASE_URL.
3. Bucket credentials passed as encrypted environment variables and a published bucket for public assets.
4. A review of which creator businesses data classes can be managed.

Tested Configuration

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

Workflow Steps

1. Model the creator businesses domain: Create tables for customer_workspaces, content_items, customer_assets, releases, and state_transitions, excluding sensitive classes.
2. Model versioned documents with a state machine (draft, review, published).
3. Publish assets for released versions to the CDN bucket.
4. Serve only published versions publicly.
5. Deploy and verify the version list and a published page.
6. Run deployment command: ample deploy . --name --public --start "python3 run.py" --env S3_ENDPOINT=...
7. Verify using pattern self-test(s) and acceptance checks for the creator businesses workflow.

Examples

• Django pattern fixture: Verified relational records basis for this blueprint.
  • Source Reference: tests/deploy-canaries/django-patterns

Success Checks

• App responds on its public URL expected as ample canary django patterns.
• Run relational-records self-test from the example to validate.

Limitations

• No health, financial, privacy, or compliance claims are made; validated only with the Django relational records basis.
• Confirmed only on python-3.12 template; availability of other configurations is uncertain.

Evidence Summary

• Pattern fixture checks passed under the verified creator businesses schema.
  • Last Verified: 2026-09-20T03:31:44Z

Estimated Cost

• Monthly Amount: $10.00 USD
  • Components:
    • App server: s-1vcpu-1gb at $5.00
    • Managed PostgreSQL database at $5.00
  • Note: Prices based on size from pricing.

Next Actions

1. Browse the catalog index.
2. Search published recipes by intent, stack, and constraints.
3. Prepare a side-effect-free deployment plan for an authorized project.