Skip to content
cursareDocs
Sign inGet started

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
  • Links
  • Insights and reports

Admin

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

Developer

  • Integrations
  • Google Classroom
  • Open Badges
  • Zoom
  • Learner UI registry
  • API keys & webhooks
  • MCP server
  • API reference
Explore the API

Content components

Cursare stores one native ProseMirror document: header nodes followed by typed blocks. The editor and API produce the same current schema, and the learner view renders it without loading an editor runtime or a legacy converter.

Cursare content editor showing rich learning material

Writing and structure

Use paragraphs, headings, quotes, dividers, bullet and numbered lists, tables, links, inline code, emphasis, underline, highlight, inline math, and glossary terms. H2 headings start learner steps. Progress, notes, answers, votes and references use only identities declared behavioral by the component registry. Arbitrary font and text-color styling is not supported.

Checkbox lists are intentionally unsupported. Use a normal list or a graded activity when state must be recorded.

Rich containers

  • Callout highlights a note, tip, or warning.
  • Steps is the single ordered-presentation component.

Slides, tabs, and timelines are intentionally absent. Use Steps so authors and AI generation have one predictable structure.

Media and technical content

  • Image is a block with a URL-or-upload source line, metadata and accessible alternative text; there are no inline images.
  • Video and Audio support uploaded learning resources. Other files are not blocks: upload one from the link tool (or drop it into a paragraph) and it becomes a download link on its own name.
  • Embed accepts validated HTTPS providers, including Cal.com without dedicated booking semantics.
  • Code block is the single code presentation component.
  • Math renders display LaTeX; inline math belongs inside prose.

The content image is canonical everywhere: editor, cards, storefront, learner view, Open Graph, and social metadata. There is no separate SEO image.

Callouts, quotes, steps, list items and table cells hold prose only (paragraphs, lists and code); a component never nests another component. Images, video and audio render as soon as their link resolves; only third-party iframe embeds wait for an explicit activation. Unfinished source text remains saveable and inert, but unresolved media blocks cannot be published. Diagrams and opaque compatibility nodes are not part of this schema.

Practice and assessment

  • Poll is ungraded; votes reference the poll's stable behavioral id and can expose the cohort distribution.
  • Quiz grades multiple-choice questions on the server.
  • Open response collects written answers and supports author-only reference answers and evaluation criteria.

Correct answers, reference answers and evaluation criteria remain in the author document and are removed from learner payloads before delivery.

References

A Reference composes another published content into the current learning path. Its stable placement ID, target content ID, route segment, title, pacing, and prerequisites belong to the parent document. Publication rejects missing, unpublished, cross-organization, self-referential, or cyclic targets atomically.

Removed alternatives

Cursare no longer supports Slides, Accordion, Reveal, Flashcards, Cloze, Matching, Ordering, Code Tabs, Code Diff, Content Tabs, Timeline, or checkbox lists. This is a breaking authoring contract; there is no legacy document compatibility layer.

PreviousEditor and blocksNextPublishing and access

Your privacy choices

The technical Tag Manager container is required to apply your choices. Analytics and marketing cookies and storage remain optional and stay off until you authorize them. Privacy Policy.

Sign-in, security, core functions and consent enforcement.

Audience measurement such as Google Analytics.

Marketing storage, campaign attribution and optional tags.