Publishing Updates to Your Listed Lessons

If your lesson is listed on the marketplace, the Studio's top bar gains a small publish status next to the auto-save indicator. It answers the question that matters once other educators are using your lesson: _are my latest edits live for buyers, or only saved to my draft?_

This status appears only for listed lessons. A lesson you have not listed shows just the auto-save indicator — there is nothing to publish, because assigning it to a classroom already delivers a pinned snapshot to your own students.

What the publish status tells you

You'll see one of three states:

• Published v3 with a checkmark — your live, listed version is v3, and your draft matches it. Buyers are seeing exactly what you see. Nothing to do.
• Unpublished changes since v3 · View with a Publish v4 button — you've edited and saved your draft since you last published, so your draft is now _ahead_ of what buyers see. Publish v4 pushes those changes live as a new version; clicking the badge itself opens History at v3, showing the changes Berdee recorded since buyers' current version.
• Not published with a Publish button — the lesson is listed but you haven't published a version yet. Publishing makes your draft the first buyer-visible version.

The version number (v3, v4, …) goes up by one each time you publish a genuinely changed draft, so it doubles as a simple history of how many updates buyers have received.

Saving is not publishing

This is the key distinction, and it's the same one described in Saving and auto-save:

• Auto-save keeps your _private draft_ current as you edit. No buyer or student sees your draft.
• Publishing takes a snapshot of your saved draft and makes it the version buyers receive.

So you can edit freely — fix a typo, rework a scene, try something out — and every change is saved to your draft, while buyers stay on the last version you published. The Unpublished changes badge is simply the Studio reminding you that your draft has moved ahead of the live version, in case you meant to push those updates out.

How to publish an update

1. Make and save your edits (auto-save handles the saving).
2. When you're ready, click Publish (or Publish v4) in the top bar. A short confirmation appears before anything goes live.
3. In the confirmation, you'll see how many educators own this lesson — the people who will receive this update — and an optional "What changed?" box.
4. Add a release note if you like (see below), then click Publish to confirm. The status updates to Published v4 — your changes are now live for buyers.

Nothing publishes on the first click: the confirmation is your chance to review who this reaches and jot down what changed before it ships. If your draft already matches the live version, the confirmation tells you there are no changes to publish and the button stays disabled, so you never ship an identical version by accident.

Adding a release note

The "What changed?" note is optional, but it's the simplest way to tell buyers what's new. It shows up in the lesson's version history, so an educator who owns your lesson can glance at "Fixed a typo in scene 2" or "Added a new practice round" and know whether to take a closer look — see Your purchased lessons keep improving. Leave it blank and the version simply publishes without a note.

Suggest a note from your history

Under the note box you'll find Suggest from history. Click it and Berdee drafts a note for you from the changes it recorded since your last published version — things like "Added a new scene" or "Reworded a question", written for a buyer rather than as an edit log. Small tweaks such as moving or resizing something are left out, because they aren't what a buyer needs to know.

It's a starting point, not a submission:

• Nothing happens until you click. Your history isn't read, and nothing lands in the box, unless you ask for it.
• The draft lands in the box, and it's yours to change. If you'd already started typing, the suggestion is added below what you wrote, after a blank line. Rewrite it, trim it, or delete it entirely.
• Only what's in the box when you press Publish reaches buyers. The suggestion names your scenes and widgets by the names you gave them, so it's worth a read before you publish — those names are private to you until you choose to send them out.

The button appears once you've published at least one version; on a first publish there's nothing to compare against yet. If nothing was recorded since your last published version, it says so rather than inventing a note — and if Berdee can't read your recorded history at all (recording is paused, or the read didn't succeed), it says that instead, which is a different thing and never gets reported as "nothing changed". Either way the box is left exactly as you had it, and Publish is never held up by it: you can always write your own note, or publish without one.

Buyers who own your lesson automatically receive the new version. Students keep working from the version that was assigned to them, so no one is disrupted mid-lesson.

To adjust your listing's price and details, do that from the full listing flow described in Publishing to the marketplace.

If you restore an earlier draft

Looking back through History and restore and putting your draft back to an earlier point changes your draft only. Buyers stay on the version you last published; the top bar simply flips to Unpublished changes, the same as it would after any other edit.

So restoring is safe to do on a listed lesson: nothing reaches buyers until you publish. When you are ready to send the restored content out, publish it exactly as you would any other update. And if the restore left your draft identical to what buyers already have, the confirmation tells you there are no changes to publish — nothing to do.

When Berdee blocks a publish

Berdee checks your draft for a short list of problems that would reach buyers broken — a Submit button with nothing to submit, a scene that navigates to something that isn't a scene, and a few others. If any are flagged, a validation issues badge appears in the top bar; open it to see what's wrong and jump straight to the scene. Publish stays blocked until they're resolved.

One worth knowing about by name: a condition that checks a deleted or renamed option. If a condition compares a dropdown's answer, or a spin wheel's landed segment, against an option that no longer exists — say you renamed "Paris" to "Paris, France" but a condition still checks for "Paris" — that branch can never match again. An is condition like that blocks publish (and blocks assigning the lesson straight to a classroom) rather than let a dead path ship quietly; an is not condition only gets a warning, since it's now always true instead of unreachable. See Renaming an option a condition points at for how to spot and fix it.

Tips

• Watch for Published v{n} with a checkmark before you step away — it confirms buyers are on your latest work.
• An Unpublished changes badge is never a problem on its own; it just means your draft is ahead. Publish when your changes are ready, not before.
• The publish status is for _listed_ lessons only. To deliver an updated lesson to your own classroom, assign it (or push the latest version) from the classroom instead — see Push a new version to students.