Getting started

This guide walks through the complete path to your first learning experience on Cursare: creating the organization, creating content, writing it in the editor, optionally configuring an offer, checking it as a learner, publishing, and sharing. Each step is short enough that you can validate the entire platform in a single session.

On Cursare, Content is the single authoring unit. It may be a standalone lesson, a reusable module, or a complete program composed from references to other contents. Those are starter templates, not persisted types. Publishing makes a version available; adding an Offer makes a published root enrollable or sellable.

Flow overview

The path to your first content has seven steps. Each one is reversible: nothing new is visible to the learner until you publish.

Before you begin

Content always belongs to an organization, and you must be a member of it to create and edit. Confirm the organization's name, its visual identity, and who is involved in the operation. These details can be adjusted later in Settings, without blocking content creation.

If your organization works with teams, decide early whether the content will be personal (belonging to the creator) or a team's. Creating content inside a team's portfolio requires you to be part of it — or to be an owner/admin of the organization.

Step 1 — Prepare the organization

Review the organization's identity before exposing any content to the public: name, logo, and the public slug, which forms the canonical URL of your offerings. Nothing here blocks content creation, but the organization's name appears as the publisher on public pages and in the catalog.

Step 2 — Create the content

1. Go to Content in the dashboard and choose New.
2. Type the title — the handle (the URL identifier) is derived from it automatically, and you can edit it before confirming.
3. Choose a neutral starter: Blank, Lesson, Module, or Program.
4. Choose the owner: personal or a team.

That act creates one unpublished content and no offer. Every starter produces the same entity and only changes the initial blocks. Add an offer later if this content should become an enrollment root; referenced content needs no offer.

The handle is validated at creation and must be unique within the organization. The rules:

The content's internal identifier (the id) is the stable identity across the entire platform — enrollments, purchases, reviews, quiz history, and references point to it. That's why the handle can be renamed later without breaking these links; only the old public links stop resolving.

Step 3 — Write in the editor

Open the Content tab of the editor and write the first section. The editor combines free writing with structured blocks: paragraphs, headings, lists, quotes, code, and tables form the narrative; blocks come in when you need media, navigation, or interaction.

• Use headings to split the reading into understandable steps — they also define the sections that anchor the learner's progress.
• Type / to open the block menu and insert media, activities, or references.
• Write clear names from the start: they appear in the dashboard, in the catalog, and in the learner experience.

The draft is saved as you work. For the step-by-step of writing, see Editor and blocks; for the full block library, see Blocks.

Step 4 — Review price, access, and catalog

If the content should accept enrollment or payment, create an offer from Offers. The first active offer becomes the default atomically. Each offer can define its own price, installments, seats, access, approval, and delivery. Content with no active offer remains reusable and cannot receive new enrollments.

For additional offers, campaigns, seats, and the buyer checkout, see Pricing & checkout. For the access models and progressive release, see Publishing and access.

Who can edit what

Editing is divided by role domains. Organization owners and admins have access to everything; delegates only see their own domain.

Step 5 — Review as a learner

Turn on Learner preview in the editor. The preview removes the authoring controls and reproduces the reading, navigation, and activities exactly as the learner will see them. Cards appear only when they are part of the interaction — quiz, reference, or media — and the rest follows the page's normal flow.

Check especially:

• the pacing between headings, text, and interactive blocks;
• the legibility of images, video, and tables;
• the options and feedback of the activities;
• the references to other modules;
• the behavior at a smaller screen width.

Step 6 — Publish

When the content is ready, publish the current version. Publishing:

• copies the draft to the published version — what the learner now reads;
• records the publication date;
• recomputes the sections (to anchor progress) and the references between modules.

Publishing happens in place: there is no separate version row. It stores the exact document and one versioned publishedManifest that preserves the ordered mix of sections and references. Progress survives reordering because it uses stable block and placement ids. Every reachable reference must point to published content in the same organization and the graph must remain acyclic. Any failure keeps the previous published document and manifest unchanged.

Step 7 — Share

After publishing and activating an eligible offer, the content page at its canonical public URL — the organization's slug plus the content handle — is live. From there you can:

• share the public link directly with learners;
• list an offer-backed content so that it appears in the catalog;
• embed the content in another site using the embed options.

Content with no active offer has no public entry page. It can still be published and reused through references inside an offered root.

Rules worth remembering

Next steps