page:blueprints:publishing:client portal:next js

Publishing: client portal using Next.js

A client portal 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;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

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: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

Representative Queries

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

Resource Requirements

• Compute
• PostgreSQL
• S3-compatible object storage

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
• S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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.

Tested Configuration

• Template: node-22
• Runtime: node
• Size: s-1vcpu-1gb
• Install: npm install
• Build: npm run build --if-present
• Start: npm run start

Workflow Steps

1. Model the publishing domain: Create the tables titles, editions, customer_workspaces, customer_assets, document_access. The catalog of titles lives in titles; keep the sensitive classes (unreleased manuscripts, royalty statements, customer license keys) out of this schema.

2. Model client entities and engagement periods; every document belongs to one engagement.

3. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).

4. Store documents in the private bucket and stream them through the app.

5. 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=...

6. Verify: Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the publishing workflow.

   Command: ample logs --kind build

Success Checks

• app responds on its public URL
  • Kind: http_get
  • Path: /
  • Expect: ample canary next js patterns
• private-document-library self-test from the example
  • Kind: http_get
  • Path: /p/private-document-library
  • Expect: see the pattern fixture checks

Limitations

• The technical basis (private document library 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.