page:blueprints:publishing:asset library:next js

Publishing: Asset Library Using Next.js

A asset library blueprint for publishing built with Next.js on Ample. Domain schema:

• titles (isbn_or_slug, title, author, imprint, published_at): the catalog of titles;
• editions (title_id, format, version, object_key): editions and versioned files;
• customer_workspaces (name, license_type, seat_count): institutional or trade customers;
• customer_assets (workspace_id, title_id, object_key, license_expires_at): licensed files per customer;
• uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

Public information: title catalog and author pages, release schedules, rights and permissions contact. Kept out of scope until handling is reviewed: unreleased manuscripts, royalty statements, customer license keys. Manuscripts and royalty data are confidential; licensed files are authorized per customer workspace.

Technical basis verified on Next.js: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

Representative Queries

• Publishing: asset library using Next.js
• Where can I host Publishing: Asset library built with Next.js?
• I need a genuinely specialized asset library workflow covering editorial roles, publication versions and rights-scoped assets.

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
• A review of which publishing data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the publishing domain: Create the tables titles, editions, customer_workspaces, customer_assets, uploads. The catalog of titles lives in titles; keep the sensitive classes (unreleased manuscripts, royalty statements, customer license keys) out of this schema.
2. Workflow step 1: Model assets linked to their owning group or workspace
3. Workflow step 2: Validate uploads and store them in the private bucket; link each object to its row
4. Workflow step 3: Authorize downloads by membership
5. Workflow step 4: Deploy and verify rejection of disallowed files and a linked upload
6. Deploy: 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=...
7. Verify: Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the publishing workflow. Command: ample logs --kind build

Examples

• Next.js pattern fixture: Verified browser file uploads basis for this blueprint. Source Ref: tests/deploy-canaries/next-js-patterns

Success Checks

• App responds on its public URL: expected response at / is "ample canary next js patterns"
• Browser-file-uploads self-test from the example: expected response at /p/browser-file-uploads is "see the pattern fixture checks"

Limitations

• The technical basis (browser file uploads on Next.js) was verified with the pattern fixture; the publishing 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. Manuscripts and royalty data are confidential; licensed files are authorized per customer workspace.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• 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
• Components:
  • App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  • Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 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.

Evidence Summary

• 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 browser file uploads checks passed: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). The blueprint's Publishing schema and workflow below build on that verified basis and were not separately executed. Observed at: 2026-09-21T02:34:39Z.

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Publishing: GET /v1/catalog/nodes/industry%3Apublishing
• Browse Asset library: GET /v1/catalog/nodes/workload%3Aasset-library
• Browse Next.js: GET /v1/catalog/nodes/stack%3Aframework-next-js
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app