page:blueprints:tutoring centers:member portal:next js

Label

Tutoring centers: member portal using Next.js

Summary

A member portal blueprint for tutoring centers built with Next.js on Ample. Domain schema:

• course_groups (subject, level, start_at, end_at, capacity): tutoring groups;
• memberships (course_group_id, student_reference, guardian_reference, role): students, guardians and tutors;
• sessions (course_group_id, starts_at, tutor, attendance_count): session events;
• materials (course_group_id, title, object_key, visibility): worksheets and answer keys;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

Public information: subjects and levels, schedule and locations, tutor qualifications. Kept out of scope until handling is reviewed: minor students and guardian identity, progress reports. Data about minors is sensitive; only group schedules and materials are modeled here. 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).

Framework

Next.js

Workload

Member portal

Industry

Tutoring centers

Release Status

published

Support Status

verified

Execution Status

ready

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 tutoring centers data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the tutoring centers domain: Create the tables course_groups, memberships, sessions, materials, document_access. Tutoring groups lives in course_groups; keep the sensitive classes (minor students and guardian identity, progress reports) 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.
7. Verify: Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the tutoring centers workflow.

Examples

• Next.js pattern fixture: Verified private document library basis for this blueprint.
  Source Ref: tests/deploy-canaries/next-js-patterns

Success Checks

• App Response Check: app responds on its public URL
  Kind: http_get
  Path: /
  Expect: ample canary next js patterns
• Private Document Library Check: 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 tutoring centers 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. Data about minors is sensitive; only group schedules and materials are modeled here.
• 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.