Overview
Cursare is a platform for building, publishing, selling, and tracking learning experiences. This page is the map of the documentation: it explains how the platform is organized and points you to the main areas (the sidebar lists every page).
What Cursare is
Cursare brings everything a teaching operation needs into one place: writing the material, defining how it's delivered, controlling who has access, charging when it makes sense, and observing what happens after enrollment.
Instead of splitting "course," "lesson," and "path" into separate products, the platform works with a single flexible unit — content — that can grow from a standalone lesson into a full library without duplicating the original material.
How the platform is organized
Content is the central authoring unit: it owns identity, the canonical document, and its published learning graph. An explicit offer owns sellability, price, access, approval, and delivery terms. Publishing, enrollment, payment, cohort, and tracking connect these two boundaries without moving commercial state into the document.
The same piece of content can play different roles depending on context:
| Role | How it works |
|---|---|
| Root | Content connected to an explicit offer — the single enrollment and access boundary |
| Reusable content | Content referenced by one or many roots, without a second enrollment |
| Composed experience | Any content that references other content at one or many levels |
A reference connects one content to another without copying it: the target stays single and can appear across many paths, each with its own title, address, and release schedule. Offers decide what is sellable; references decide how learning is composed.
Recommended path
If this is your first time on the platform, follow this order:
- Getting started — set up your organization, create a short piece of content, and walk the learner's path.
- Concepts — understand content, references, access, and progress before you scale.
- Editor and blocks — write the material and add media, activities, and assessments.
- Publishing and access — review in the learner preview and put the version into circulation.
- Sales and payments — add an offer only when a published root should accept enrollment or payment; reusable content can remain offerless.
Documentation areas
Quick map by goal
| You want to... | Go to |
|---|---|
| Publish something for the first time | Getting started |
| Understand the architecture before you scale | Concepts |
| Write and structure the material | Editor and Block reference |
| Control publishing and who has access | Publishing and access |
| Track learners and enrollments | Learners and enrollments |
| Measure progress and issue certificates | Progress and certificates |
| Charge for a piece of content | Offers & checkout |
| Organize content owners | Teams |
| Analyze outcomes | Insights |
| Adjust the organization and security | Organization & security |
| Integrate via code | API Reference |
Conventions in these docs
- Content, Basics, Catalog, Access, Pricing, Settings, and similar names in
coderefer to areas and labels in the product interface itself. - Callout blocks highlight rules and things to watch for: neutral information appears as a note, confirmations as success, and risks as a warning.
- Links in the
/docs/...format point to other pages within this same documentation.
If this is your first time on the platform, start with Getting started. If you'd rather understand the model before you build, start with Concepts.