Law firms: form collection using Next.js · Ample Computer

Law firms: form collection using Next.js

A form collection blueprint for law firms built with Next.js on Ample. Domain schema:

Public information: practice areas and attorney profiles, intake process and fee structure overview, office locations. Kept out of scope until handling is reviewed: privileged communications and case files, identity and financial documents, opposing-party information. Matter documents are privileged; the portal models per-matter authorization. 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).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the law firms domain. Create the tables client_entities, matters, document_requests, shared_documents, uploads. Clients with conflict-check status live in client_entities; keep the sensitive classes (privileged communications and case files, identity and financial documents, opposing-party information) out of this schema.

  2. Workflow step 1. Model document requests per engagement with due dates and status

  3. Workflow step 2. Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request

  4. Workflow step 3. Authorize uploads by client entity

  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.

$ 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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the law firms workflow.
$ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary next js patterns”
✓ browser-file-uploads self-test from the example · http get/p/browser-file-uploads → “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 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 Law firms schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover