START
P2LRN Documentation
Start by understanding what P2LRN is and what a package contains. Then do a simple first integration with CDN, prepare the installation you are going to use and continue with creation, playback and integration. Progression and metrics appear later, together, when you already need real monitoring of learning.
Recommended path
Before you start
Learn the pieces of P2LRN, the fundamental concepts, and what a package actually contains.
2 · PROBARQuick start
Do a first integration of the Player with CDN and an example package before entering into the full installation.
3 · PREPARARInstallation
Incorporate P2LRN into your project. The documentation presents CDN first and then NPM.
4 · CREATECreate the course
Use Studio for visual authoring or Toolkit for code authoring.
5 · PLAYTry with Player
Open the package, check content and activities and verify that the experience works.
6 · INTEGRARConnect your platform
Connect users, permissions, persistence, events, verified resources, and live capabilities. Multi-user collaboration continues in its specific guide.
7 · FOLLOW-UPProgression and metrics
When you already need tracking, define how the learner progresses and how to convert that execution into metrics and analytics.
AI, LMS and LTI 1.3 Connectors
Check out new integrations for ChatGPT, Claude, Grok, local AI tools, and educational platforms Moodle, Canvas, Sakai, Chamilo, and Open edX.
P2LRN skills to create courses with AI
Download versions for ChatGPT, Claude, Gemini CLI and Grok Build. Generate and validate files .p2lrn using Python, without confusing the Skills with the MCP connector or the Studio editor.
What should be understood before the first integration
These three pages form the block Before you start. They are the vocabulary and the minimum structure necessary to understand the rest; They focus on concepts prior to installation, monitoring, persistence and analytics.
What Studio, Toolkit, Player and your own platform do, and which one you need for each task.
Authoring project, package, manifest, graph, resources, representations, profiles and renderers.
What the package physically contains, how it is organized, and what data belongs to the host and not the course.
Progression and metrics go together, but more later
They are two parts of the same tracking problem, but they are not part of the introduction. Progress explains the rules that the course declares—mandatory, completion, approval, blocking, and unblocking. Metrics and analytics explains what actually happened during the execution and what data the platform should retain or analyze.
First understand the format, install, create and play. When you need to connect the learner journey with status, notes, events, and reports, go to Tracking and read Progression → Metrics and Analytics as a continuous block. To later view that data in an embeddable panel, continue in the section Analytics.
Analytics
P2LRN Analytics It now has its own section of the documentation. The embeddable dashboard brings together learners, courses, progress, activity, attempts, tracking signals, and authoritative notes without saving private data within the package .p2lrn.
Summary, learners, courses, notes and activity with filters, pagination and CSV export.
Connect an authorized endpoint using src or createHttpAnalyticsDataSource; Identity, permissions and persistence remain on your platform.
Can be loaded from /analytics/current/dist/ or install as @p2lrn/analytics, maintaining the same version as the rest of the P2LRN packages.
The public Analytics app allows you to review the component and its navigation with a demo dataset.
If you only want to create a course with the hosted Studio
you can open Studio directly without installing anything. The installation phase is only necessary when you want to incorporate P2LRN into your own project or use the Toolkit from code.
If you want to send it to a learner without an LMS
Studio can generate a self-running offline delivery: the learner opens it in his browser, completes the activity and returns a single .p2lrn-result to review it later in Studio.
Responsibility of each piece
Visual editor to build courses, lessons, images, resources, games and collaboration.
API and CLI for creation, validation, reading and transformation.
Opens, verifies, and plays the package, negotiates capabilities, and emits events.
Preserve users, permissions, progress, scores, collaborative services, verified resources, and secrets.
reading rule
Before you start It only groups Component Map, Fundamental Concepts and P2LRN Format. Quick start allows you to test the Player with CDN before entering the full installation. Next comes installation, creation, reproduction and integration. Tracking It groups Progression and Metrics and analytics because one defines the rules of the journey and the other measures its results.