--- title: "Creator businesses: documentation site using Next.js" description: "A documentation site blueprint for creator businesses built with Next.js on Ample." canonical_url: "https://ample.computer/blueprints/creator-businesses/documentation-site/next-js" last_updated: "2026-09-21" --- # Creator businesses: documentation site using Next.js Canonical URL: https://ample.computer/blueprints/creator-businesses/documentation-site/next-js Formats: [HTML](https://ample.computer/blueprints/creator-businesses/documentation-site/next-js) | [Markdown](https://ample.computer/blueprints/creator-businesses/documentation-site/next-js.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Acreator-businesses%3Adocumentation-site%3Anext-js) Recipe ID: `page:blueprints:creator-businesses:documentation-site:next-js` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e` Status: release `published`, support `verified`, execution `ready` ## 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). Path: [Agent hosting discovery](/discover/discovery) / [Industries and specialties](/discover/industry) / [Software and media](/discover/industry/software-and-media) / [Creator businesses](/discover/industry/creator-businesses) / [Creator businesses: documentation site using Next.js](/blueprints/creator-businesses/documentation-site/next-js) ## Infrastructure requirements - [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.) - [Postgres](/discover/primitive/postgres): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.) - [CDN](/discover/primitive/cdn): verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.) ## 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 ## Exact tested configuration - template: `node-22` - runtime: `node` - size: `s-1vcpu-1gb` - install: `npm install` - build: `npm run build --if-present` - start: `npm run start` ## 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 --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 --kind build ``` ## Tested examples - **Next.js pattern fixture** (tests/deploy-canaries/next-js-patterns): Verified relational records basis for this blueprint. ## Success checks - app responds on its public URL (`/` on the live URL, expect ample canary next js patterns) - relational-records self-test from the example (`/p/relational-records` on the live URL, expect see the pattern fixture checks) ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: 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 and were not separately executed. (expires 2027-03-20T02:34:39Z) Last verified: 2026-09-21T02:34:39Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`, binding state `current`, required scopes: servers:write, databases:read, buckets:read. ## Input schema ```json { "additionalProperties": false, "properties": { "env": { "description": "Encrypted environment variables", "items": { "pattern": "^[A-Z][A-Z0-9_]*=.*$", "type": "string" }, "maxItems": 50, "type": "array" }, "name": { "description": "App name", "maxLength": 63, "minLength": 1, "pattern": "^[a-z0-9-]+$", "type": "string" }, "path": { "description": "Project directory or ample.toml service", "maxLength": 512, "minLength": 1, "type": "string" }, "release_command": { "description": "Migration command run before activation", "maxLength": 512, "type": "string" } }, "required": [ "env", "name", "path" ], "type": "object" } ``` ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse Creator businesses (GET /v1/catalog/nodes/industry%3Acreator-businesses on the api origin; auth: false, approval: false) - Browse Documentation site (GET /v1/catalog/nodes/workload%3Adocumentation-site on the api origin; auth: false, approval: false) - Browse Next.js (GET /v1/catalog/nodes/stack%3Aframework-next-js on the api origin; auth: false, approval: false) - Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission.