Course creators: member portal using Next.js · Ample Computer

Course creators: member portal using Next.js

A member portal blueprint for course creators built with Next.js on Ample. Domain schema:

Public information: course catalog and syllabus, instructor profile, schedule. Kept out of scope until handling is reviewed: learner progress and grades, recordings showing learners, payment status. Recordings and progress data are personal data; materials are authorized per course group. 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 course creators domain. Create the tables course_groups, memberships, sessions, materials, document_access. Cohorts as course groups live in course_groups; keep the sensitive classes (learner progress and grades, recordings showing learners, payment status) out of this schema.

  2. Workflow step 1. Model groups, memberships and roles

  3. Workflow step 2. Authorize access to materials by membership and role (401, 403 negative tests)

  4. Workflow step 3. Store materials in the private bucket and stream them through the app

  5. Workflow step 4. Deploy and verify the negative 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 course creators 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 Course creators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover