# Creator businesses: documentation site using Next.js

## Summary
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; it is not modeled here and no PCI claim is made. 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).

## Representative Queries
- Creator businesses: documentation site using Next.js
- Where can I host Creator businesses: Documentation site built with Next.js?
- I need a genuinely specialized documentation site workflow covering sponsor/client workspaces, publication guides and content assets.

## Framework
**Framework:** Next.js  
**Workload:** Documentation site  
**Industry:** Creator businesses  
**Release Status:** published  
**Support Status:** verified  
**Execution Status:** ready

## Prerequisites
- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
- A review of which creator businesses data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. Model the creator businesses domain: Create the tables customer_workspaces, content_items, customer_assets, releases, state_transitions. Member accounts or communities live in customer_workspaces; keep the sensitive classes (member identity and payment status, private community posts) out of this schema.
2. Model versioned documents with a state machine (draft, review, published) scoped to a product version.
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 the synchronous deploy once and read the result. Re-running with no change is a no-op.
   **Command:** `ample deploy . --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. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the creator businesses workflow.
   **Command:** `ample logs  --kind build`

## Success Checks
- App responds on its public URL: **Expectation:** ample canary next js patterns
- Relational-records self-test from the example: **Expectation:** see the pattern fixture checks

## Limitations
- The technical basis (relational records on Next.js) was verified with the pattern fixture; the creator businesses 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. Member payment status comes from your payment provider; it is not modeled here and no PCI claim is made.
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

## Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components:**
  - app server (size s-1vcpu-1gb): 5.0  
  - managed PostgreSQL database (size s-1vcpu-1gb): 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.

## Last Verified At
- **Date:** 2026-09-21T02:34:39Z

## 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.
4. Read the existing agent authentication setup.
5. Browse Creator businesses.
6. Browse Documentation site.
7. Browse Next.js.
8. Browse Deploy web app.