Course creators: member portal using Next.js

Summary

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

• course_groups (name, start_at, end_at, capacity): cohorts as course groups;
• memberships (course_group_id, member_email, role, joined_at): learner and instructor membership;
• sessions (course_group_id, starts_at, title, recording_object_key): session events and recordings;
• materials (course_group_id, title, object_key, visibility): teaching materials;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.
  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).

Representative Queries

• Course creators: member portal using Next.js
• Where can I host Course creators: Member portal built with Next.js?
• I need a genuinely specialized member portal workflow covering course structure, member entitlements and downloadable materials.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive: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.

Workflow 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 sensitive classes (learner progress and grades, recordings showing learners, payment status) out of this schema.
2. Model groups, memberships, and roles.
3. Authorize access to materials by membership and role (401, 403 negative tests).
4. Store materials in the private bucket and stream them through the app.
5. Deploy and verify the negative tests and an authorized download.
6. 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. Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the course creators workflow.
   • Command: ample logs --kind build

Examples

• Next.js pattern fixture:
  Verified private document library basis for this blueprint.

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 course creators 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. Recordings and progress data are personal data; materials are authorized per course group.
• 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.