Overview

Cursiva 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 every area.

What Cursiva is

Cursiva 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, community, and tracking all orbit around it.

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

Role	How it works
Standalone lesson	A piece of content published on its own and consumed directly
Sellable offer	A piece of content with a price, checkout, and access rules
Composed experience	A piece of content 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.

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 — turn published content into an offer 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.Pricing & checkoutPrices, coupons, 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 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	Pricing & 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 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.