GET STARTED / COMPONENTS
Component Map
P2LRN is divided into small pieces with different responsibilities. Choosing the right part avoids duplicating functions of your application within the package.
1. The complete tour
Studio and Toolkit produce or modify the package. Player plays it. Host Adapter communicates status, score, events, and resources; Capability Broker connects optional live services such as collaboration without introducing endpoints or credentials into the course.
2. Main components
Visual editor for courses, images, quizzes, games, collaboration, shared resources, and activity groups.
Portable content without external dependencies, including text, image, video, Warning, tabs and timeline.
Authoring/Reader/validation/conversion, Reference Host and CLI.
Open and check the package, negotiate capabilities, and play renderings.
Status, score, events and protected resources.
Optional live services like collaboration/AI without giving secrets to the course.
Local state and ordered outbox; You can synchronize when the network returns.
Preserve verified bytes of the course to reopen offline. Does not contain learner status.
Shared content-addressed library verified by SHA-256.
Server-side reference to separate evidence from official status/note browser.
Extract document structure to decide how to convert it to content.
Verified transport of large resources outside the main file.
3. Which component to use depending on the task
Host Adapter and authorized backend; uses the Authoritative Reference Host as a pattern, not as an identity system.
Offline Host Adapter for state/outbox and Package Cache for course bytes.
Resource Library or remote representation with expectedDigest + resolver verificado.
Capability Broker + Host collaboration provider.
Player/Host directo o proveedor LTI 1.3 self-hosted.
Reader.
4. What should not be kept inside the package
The package contains structure, content, profiles and portable metadata. It should not be converted into a user database. Identity, passwords, permissions, license plates, secrets, individual progress and private data remain on the platform.
5. How the installation fits
NPM and CDN are ways to load browser components; They are not different products. Once the installation path is chosen, the Player or Studio API is the same for that version.