Architecture practices: client portal using Next.js · Ample Computer

Architecture practices: client portal using Next.js

A client portal blueprint for architecture practices built with Next.js on Ample. Domain schema:

Public information includes: portfolio and services, team and accreditations, studio locations. Kept out of scope until handling is reviewed: unreleased drawings and site surveys, planning submissions before filing, client contact details. Drawings and surveys are client-confidential until issued; the portal models per-project authorization only. 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).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the architecture practices domain. Create the tables client_entities, projects, drawing_sets, approvals, document_access. Clients and project sites live in client_entities; keep the sensitive classes (unreleased drawings and site surveys, planning submissions before filing, client contact details) out of this schema.
  2. Workflow step 1. Model client entities and engagement periods; every document belongs to one engagement.
  3. Workflow step 2. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
  4. Workflow step 3. Store documents in the private bucket and stream them through the app.
  5. Workflow step 4. Deploy and verify the negative authorization tests and an authorized download.
  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/private-document-library) and your own acceptance checks for the architecture practices workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary next js patterns”
✓ private-document-library self-test from the example · http get/p/private-document-library → “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 private document library checks passed: 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). The blueprint's Architecture practices schema and workflow build on that verified basis.

Tested examples

What it doesn’t cover