# Professional training: member portal using Next.js

A member portal blueprint for professional training built with Next.js on Ample. Domain schema: 
- **course_groups** (certification, cohort, start_at, end_at): certification cohorts;  
- **memberships** (course_group_id, participant_email, employer, role): participants and trainers;  
- **sessions** (course_group_id, starts_at, module, location_or_link): training sessions;  
- **materials** (course_group_id, module, object_key, visibility): course materials and exam guides;  
- **document_access** (document_id, principal_reference, role, granted_at): who may read which document.

Public information: certification catalog, cohort dates, trainer credentials. Kept out of scope until handling is reviewed: exam results, employer billing, participant identity. Exam results and certifications are personal records; only cohort logistics and materials are modeled. 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  
- Professional training: member portal using Next.js   
- Where can I host Professional training: Member portal built with Next.js?   
- I need a genuinely specialized member portal workflow covering course cohorts, enrollment events and learning-resource access.

## Resource Requirements  
- **primitive:compute**  
- **primitive:postgres**  
- **primitive:s3-compatible-object-storage**

## Infrastructure Requirements  
1. **Compute**  
   - Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
2. **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.  
3. **S3-compatible object storage**  
   - Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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

## Workflow Steps  
1. **Model the professional training domain**  
   - Create the tables course_groups, memberships, sessions, materials, document_access. Certification cohorts live in course_groups; keep the sensitive classes (exam results, employer billing, participant identity) 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.  
   - 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. **Verify**  
   - Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the professional training workflow.

## Limitations  
- The technical basis (private document library on Next.js) was verified with the pattern fixture; the professional training 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. Exam results and certifications are personal records; only cohort logistics and materials are modeled.  
- 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.

## Cost Estimate  
- **Currency**: USD  
- **Monthly Amount**: $10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:  
   - app server: size s-1vcpu-1gb, quantity 1.0, monthly amount $5.0  
   - managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount $5.0  
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Next Actions  
1. **Browse the catalog index**  
2. **Search published recipes by intent, stack and constraints**  
3. **Prepare a side-effect-free deployment plan for an authorized project**  
4. **Read the existing agent authentication setup**  
5. **Browse Professional training**  
6. **Browse Member portal**  
7. **Browse Next.js**  
8. **Browse Deploy web app**

## Evidence Summary  
- Next.js pattern fixture deployed on Ample; the private document library checks passed.