Define one lesson and its audience
This workflow is for trainers, teachers and technical speakers preparing one interactive lesson, not generating a generic article or replacing a learning platform. Record the learning outcome, approved claims, presenter and expected duration. Identify the audience package separately from the private working source. Remove learner identities, credentials and confidential examples before using helpers that may process inputs on servers.
Preserve the slide dialect while reviewing
Keep baseline Markdown and JSON. The studio uses headings, page separators, speaker-note markers and reveal/quiz directives. A general Markdown linter can flag intentional repeated headings or change significant spacing. Work on a copy, explain findings and verify accepted edits in the studio rather than auto-fixing the whole deck blindly.
The Markdown link checker is static: syntax, reference and anchor findings do not establish HTTP availability. Open needed links separately and verify anchors in the actual deck. Prepare a fallback for live destinations; a link in an offline lesson does not make its target available offline.
Reconcile content, settings and visual findings
Use text diff for wording and JSON diff for slide order, layout, theme, transitions and interaction changes. Compare stable revisions, not unrelated exports, and explain regenerated identifiers rather than treating every difference as content. Check quiz choices and correct answers manually against the learning goal; a well-formed quiz can still teach an incorrect fact.
Measure actual foreground/background pairs in the selected theme. Inspect sanitized rendered HTML for common labels and structure problems where applicable. Static tools do not execute reveal sequences, certify focus behavior or guarantee accessibility. Rehearse keyboard access, visible focus, result feedback, contrast on interaction states and readability on a small screen; record unresolved issues instead of claiming certification.
Rehearse the exported file, not only the editor
Export HTML and open that exact file in the target browser. Disconnect networking and navigate every slide, reveal and quiz. Test long text, code blocks, navigation boundaries and required media. Record browser, revision and missing resources; embedded player code does not make every linked destination or external asset offline. Resolve required failures or clearly reduce the delivery promise before approval.
Audience-player code strips speaker notes, but source exports can retain them. Inspect HTML and the actual audience view, then inspect Markdown/JSON separately. Never send a notes-bearing source to an audience simply because its preview hid the notes. The studio limit is 80 slides and 2 MB; unsupported inputs need deliberate reduction, not silent omission.
Separate private sources from shared delivery
Hash the final files after the last approved edit. Keep an access-controlled presenter package with editable sources and a separate audience package with reviewed HTML. Attach revision, change ledger, rehearsal evidence, known limitations and reviewer. Hashes identify bytes, not teaching accuracy.
Publication is an optional additional step: login to publish a snapshot, then check the exact resulting audience URL and note-free content. Unlisted means not openly listed, not confidential access. Editing the source is not proof the existing snapshot changed; verify the published revision explicitly. Use general Markdown publishing, technical localization or web accessibility workflows for their wider tasks. None replaces rehearsal of this exact interactive lesson.