Skip to content
CursareDocs
Sign in

Start here

  • Overview
  • Getting started
  • Platform concepts

Create

  • Content
  • Editor and blocks
  • Block reference

Publish & access

  • Publishing and access
  • Custom domain & white-label

Learners

  • Learner experience
  • Learners and enrollments
  • Progress and certificates

Teams & cohort

  • Teams
  • Cohorts

Sales

  • Offers & checkout
  • Payments & payouts
  • Affiliates
  • Insights and reports

Admin

  • Organization & security
  • Plans, trial & billing
  • Appearance
  • Members & roles
  • Audit log

Developer

  • Integrations
  • API keys & webhooks
  • MCP server
  • API reference
Explore the API
Start here

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).

One set of docs for the whole platform

This space covers the complete workflow for administrators, authors, and learners — from the first lesson to tracking outcomes. For contracts and endpoints, see the API Reference.

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 unit. A piece of content brings together its identity, editorial body, access rules, format, and commercial setup. Publishing, enrollment, payment, cohort, and tracking all orbit around it.

The same piece of content can play different roles depending on context:

RoleHow it works
CourseThe sellable, enrollable unit — born with its offer, with a public page of its own
MaterialPure substance with no page or price, read inside the courses that reference it
Composed experienceA course that references other content as modules

A reference connects one piece of content to another without copying it: the original material stays single and can appear across many paths, each with its own module title, address, and release schedule. That's how you start with a simple lesson and evolve into courses and paths while reusing the same material.

Avoid duplicating content

Whenever the same lesson needs to appear in more than one course, reference the original content instead of copying it. Fixes made at the source propagate to every path.

Recommended path

If this is your first time on the platform, follow this order:

  1. Getting started — set up your organization, create a short piece of content, and walk the learner's path.
  2. Concepts — understand content, references, access, and progress before you scale.
  3. Editor and blocks — write the material and add media, activities, and assessments.
  4. Publishing and access — review in the learner preview and put the version into circulation.
  5. Sales and payments — every course is born with an offer; set its price if you're going to charge for it.

Documentation areas

Getting startedFrom initial setup to your first published link.Platform conceptsContent, references, composition, and access.ContentCreate, organize, and configure the central unit.Editor and blocksText, media, activities, and assessments.Block referenceEvery editor block, its fields, and its behavior.Publishing and accessPublish versions and define who can get in.Learner experienceNavigation, progress, and in-reading interactions.Learners and enrollmentsManage people, links, and ways in.Progress and certificatesSteps, prerequisites, and activity outcomes.Offers & checkoutPrices, campaigns, seats, and the buyer checkout.TeamsOrganize content owners and per-member roles.Insights and reportsAcademic and financial signals for decisions.Organization & securityOrganization profile, members, security, and plans.API ReferenceEndpoints, contracts, and authentication for integrating.

Quick map by goal

You want to...Go to
Publish something for the first timeGetting started
Understand the architecture before you scaleConcepts
Write and structure the materialEditor and Block reference
Control publishing and who has accessPublishing and access
Track learners and enrollmentsLearners and enrollments
Measure progress and issue certificatesProgress and certificates
Charge for a piece of contentOffers & checkout
Organize content ownersTeams
Analyze outcomesInsights
Adjust the organization and securityOrganization & security
Integrate via codeAPI Reference

Conventions in these docs

  • Content, Basics, Catalog, Access, Pricing, Settings, and similar names in code refer 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.

NextGetting started

Your privacy choices

Necessary cookies keep Cursare working. Analytics and marketing technologies are optional and stay off until you choose them. Privacy Policy.

Sign-in, security and core platform functions.

Audience measurement such as Google Analytics.

Tag Manager and campaign attribution.