Skip to main content

​
What LearnTerms is built around

LearnTerms gives each cohort a shared academic structure for organizing classes, modules, source documents, and questions. At a high level, LearnTerms is three things:
  1. A shared study space for the cohort
  2. An admin and contributor workflow for building study content
  3. A growing question bank organized by semester, class, and module

​
Join your cohort

To enter the right study space, you need the join code for your cohort. The cohort determines which classes, modules, documents, and questions you can access.
  1. Open the LearnTerms join flow.
  2. Enter the code your cohort was given.
  3. Confirm the class details before joining.
Once you join, LearnTerms can show you the classes and modules scoped to that cohort. That scoping matters throughout the app. The class list, module list, admin tools, and document library all depend on it.

​
How the product is organized

The app data model is intentionally opinionated:
  • A school is the top-level institution
  • A cohort groups a class year or study group inside that school
  • A semester helps organize courses across time
  • A class represents a course inside the cohort
  • A module breaks a class into smaller study units
  • A question belongs to a module
  • tags can group module content inside a class
  • Content Library documents, extracted pages, and topic maps give staff source material for question writing
This structure keeps the app relevant to the actual curriculum and gives students a consistent course hierarchy.

​
What you see first

After onboarding, most users spend their time in a few main areas:
  • Current classes
  • Module progress
  • Quick access to studying
  • Custom tests
  • Admin tools, if their role allows them
If you are a student, the main path is usually:
  1. Open your classes
  2. Enter a class
  3. Select a module
  4. Study questions or build a custom test
If you are a curator, admin, or dev, you also get access to admin routes for content management and question generation.

​
Roles matter early

Not everyone sees the same surface area of the product.
  • Students primarily consume class and module content
  • Curators can work with admin-side content tools
  • Admins can manage more of the cohort-side operational flow
  • Devs have cross-cohort operational access and can assign admin roles through the role-management UI
The permissions guide documents the exact role rules and access boundaries.