Creator businesses: documentation site using Next.js · Ample Computer

Creator businesses: documentation site using Next.js

A documentation site blueprint for creator businesses built with Next.js on Ample. Domain schema: 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: free content and previews, membership tiers, creator profile. Kept out of scope until handling is reviewed: member identity and payment status, private community posts. Member payment status comes from your payment provider. Technical basis verified on Next.js: 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 creator businesses domain. Create the tables customer_workspaces, content_items, customer_assets, releases, state_transitions. Member accounts or communities lives in customer_workspaces; keep the sensitive classes (member identity and payment status, private community posts) 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 --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/relational-records) and your own acceptance checks for the creator businesses workflow.

    $ ample logs <deployment_id> --kind build
    

How it was checked

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

Evidence

  1. November 5, 2026 · canary run
    Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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 Creator businesses schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover