Fundamental concepts

1. Authoring project (workspace) and package

A workspace is the authoring editable project: it may contain source files, configuration and intermediate data. A package .p2lrn It is the portable device that is delivered to the Player. You can keep the workspace to continue editing and publish only the generated package.

2. Manifest: identity, capabilities and integrity

The manifest identifies the package, declares profiles and entry points (entrypoints) and describes the integrity of the content. It is the first layer the Player needs to know what the course contains and what capabilities they need to understand before playing it.

3. Graph: the navigable structure

The graph describes courses, units, activities, resources and relationships. The units organize; Activities represent steps that the learner can complete; Resources point to the content that an activity needs. The entrypoints indicate from which entity a playback can begin.

4. Resource and representation

A resource can have one or more representations. The representation explains how that content is available: as a package member, embedded content, supported external resource, or another form declared by the format. Player doesn't have to guess how to open it; The representation contract indicates this.

5. Profiles: additional rules

A profile adds rules that are not part of the minimum core. Progression and questionnaires are clear examples: the manifest declares the profile and the entities use its extensions. If a rule changes navigation—for example, progression blocks—the profile must be declared at the appropriate requirement level so that an incompatible Player cannot silently ignore it.

6. Renderer and runtime environment

He renderer turns a representation into an interface for the learner. Some content also requires a execution environment isolated, for example to run external webpacks. Choosing a presentation does not change the original content: it only changes the way it is delivered when the representation is supported.

7. Player and platform

Player takes care of opening, checking and playing. The application that integrates it—the Host— deals with users, authorization and persistence. Host Adapter defines the communication between the two to load and save state, report scores, send events and resolve protected resources.

8. Integrity: trust in what is reproduced

P2LRN uses hashes and a content root to detect unexpected modifications. The goal is not just to check the initial file: the resources that the Player consumes must also respect the integrity contract. Multipart maintains that property when a resource is distributed to external parts.

9. Quick mental model