Skip to main content

πŸŽ“ Lesson 24: Capstone III β€” Publish, Test on an LMS & Course Wrap-Up

This is it β€” the finale. You'll take the course you built and get it out into the world: publish it as SCORM and HTML5, test the package, upload it to an LMS or host it on the web, verify tracking, and share it. Then we'll close the whole journey together β€” recap everything you've learned, and point you toward where to grow next. You came in a beginner. You're leaving a published course author.

πŸ“š What You'll Learn

By the end of this lesson, you will be able to:

  • Publish your course as SCORM and as HTML5 from the all-new Adobe Captivate All-New
  • Test the package before it goes live, so you catch problems where they're cheap to fix
  • Upload to an LMS (or host the web output) and verify tracking β€” completion and score reporting
  • Run a final device and accessibility check and share your course for review
  • See the whole journey in one picture, and know exactly where to grow next as an author

⏱️ Estimated Time: 40 minutes

🎯 Project: Your finished capstone, published, tested, and shared β€” the third and final deliverable. Plus a closing journal reflection on the whole course.

In This Lesson

πŸ“¦ Choose Your Publish Format

You authored in Captivate; now you publish so learners can take the course somewhere else. Publishing packages your project into a format that runs in a browser and, when needed, talks to a Learning Management System. This is Lesson 15 applied for real to your own course. The format you choose depends on where the course is going:

Format What it's for Reports to an LMS?
HTML5 Posting the course straight to the web β€” a site, a shared link, your portfolio No tracking on its own; it just plays in a browser
SCORM (1.2 / 2004) The long-standing standard most LMSs accept for tracking completion and score Yes β€” completion, score, pass/fail
xAPI (Tin Can) Richer, more detailed tracking, including some activity outside a traditional LMS Yes β€” detailed statements to a learning record store

Figure 1 β€” The common publish formats and when each fits. Your LMS's documentation says which it prefers.

For the capstone, publish both SCORM and HTML5. SCORM gives you the real, trackable LMS-ready package; HTML5 gives you a version you can drop on the web or into a portfolio without needing an LMS at all. Whichever you choose, remember the honest part: your learners never need a Captivate subscription β€” they just open a link or their LMS. The subscription is for authors like you.

πŸ’‘ Which SCORM version?

If your LMS accepts both, SCORM 1.2 is the safe, widely-compatible default; SCORM 2004 adds finer sequencing and status reporting. When in doubt, check your LMS's docs for what it recommends β€” this is one of those places where the target platform, not Captivate, makes the call.

πŸš€ Publish & Test the Package

In Captivate, open Publish and set the essentials: a clear course title, the output format (SCORM or HTML5), and your responsive/output options. For a SCORM package, you'll pick the SCORM version and confirm the tracking settings β€” the pass score and completion rules you set up while building the assessment in Lesson 23. Captivate then produces a package: a folder or a .zip, depending on the format.

⚠️ Test before you ship β€” always

The single most common cause of "my course is broken in the LMS" is publishing straight to production without testing. Don't. First, open the HTML5 output locally and click all the way through β€” every interaction, the quiz, the results slide. Then test the SCORM package in a generic SCORM tester (a SCORM Cloud-style service that simulates an LMS) to confirm it launches, tracks, and reports a score. Fixing a problem in a test environment takes minutes; fixing it after a hundred learners hit it takes an apology.

Here's the whole path from your project to a tracked result β€” the shape to keep in your head:

graph LR A["πŸ—οΈ Your .cpt
project"] --> B["πŸ“¦ Publish
SCORM / HTML5"] B --> C["πŸ§ͺ Test package
SCORM tester + local HTML5"] C --> D["⬆️ Upload
LMS or web host"] D --> E["πŸŽ“ Learner
takes the course"] E --> F["πŸ“Š Results report
completion & score"] style A fill:#bfdbfe,color:#1e293b style B fill:#bbf7d0,color:#1e293b style C fill:#fde68a,color:#1e293b style D fill:#c7d2fe,color:#1e293b style E fill:#fed7aa,color:#1e293b style F fill:#bbf7d0,color:#1e293b

Figure 2 β€” The publish-to-tracking journey: build, publish, test, upload, learner takes it, results report back. Testing is the step people skip and regret.

⬆️ Upload to an LMS & Verify Tracking

With a tested SCORM .zip in hand, uploading is usually straightforward: in your LMS, find the option to add a course or module from a SCORM package, upload the zip, and let the LMS unpack it. LMSs differ, so the exact menu varies β€” but the concept is the same everywhere: you're handing the LMS a standard package it knows how to run and track.

Then verify tracking, because publishing is only half the promise β€” the other half is that the LMS actually records what happened. Take the course as a test learner and check that:

  • The course launches and plays cleanly inside the LMS frame.
  • It records completion when you finish.
  • It records the score and the pass/fail result correctly.
  • A retake behaves the way you intended (fresh attempt, or resume).

No LMS handy? That's fine β€” this is exactly why you published HTML5 too. Host the HTML5 output on the web (any static web host works) and you have a real, shareable course link. You won't get LMS tracking that way, but you'll have a live course you can put in a portfolio and send to anyone β€” which for a capstone is a genuine win.

πŸ’‘ SCORM testing without an LMS. A generic SCORM testing service (the SCORM Cloud style of tool) lets you upload your package and see the tracking data it would report β€” completion, score, pass/fail β€” without owning an LMS. It's the standard way authors sanity-check a SCORM build, and it's how you can complete this step even if no LMS is available to you today.

βœ… Final Check & Share

Before you call it shipped, one last pass β€” the published output, not the project file, is what learners actually experience, so give it the final look.

  • Device check: open the published course on a phone and a desktop. Confirm the responsive layout holds up where it counts (Lesson 7).
  • Accessibility check: tab through a couple of slides with the keyboard, confirm alt text and captions survived publishing, and check contrast on real screens (Lesson 14).
  • Share for review: send the link to a friend or colleague and ask them to take it. Fresh eyes catch the typo you've read past twenty times and the interaction that's obvious to you but not to them (Lesson 21).

πŸŽ‰ You shipped a course

Take a second to feel this. You planned a course, built it in the all-new Adobe Captivate, published it, tested it, and put it somewhere a real learner can take it and be tracked. That is the complete professional pipeline β€” the exact thing instructional designers get paid to do. You didn't just learn Captivate; you used it, start to finish. Congratulations, genuinely.

🎯 Try It: Ship Your Capstone

πŸ‹οΈ Activity: Publish, test, and share (the final deliverable)

Objective: Get your capstone out of Captivate and into a place a learner can take it, with tracking verified where possible.

Steps

  1. Publish HTML5 and click all the way through the local output β€” every interaction, the quiz, the results. (⏱️ 8 min)
  2. Publish SCORM with your title, version, and tracking settings; note the .zip it produces. (⏱️ 8 min)
  3. Test the SCORM package in a generic SCORM tester (SCORM Cloud style) β€” confirm it launches, tracks completion, and reports a score. (⏱️ 10 min)
  4. Get it live: upload the SCORM zip to an LMS and verify tracking or host the HTML5 output on the web for a shareable link. (⏱️ 10 min)
  5. Final check & share: open it on a phone, run the accessibility check, and send the link to someone for a real take-through. (⏱️ 8 min)
πŸ’‘ Hint

No LMS? Don't skip the step β€” use a free SCORM testing service to see the tracking, and host the HTML5 build for your shareable link. That combination proves both halves (tracking works; the course is live) without owning an LMS. And if a publish setting is confusing, the safe default for SCORM is 1.2 with your pass score set β€” you can always republish; publishing is not a one-shot decision.

βœ… Activity Complete When…

  • You've published both HTML5 and a SCORM package and clicked through the output
  • You've tested the SCORM package and seen it report completion and a score
  • The course is live somewhere β€” an LMS with verified tracking, or a hosted HTML5 link
  • You've done a final device + accessibility check and shared it with at least one person

🎯 Quick Quiz

Question 1: You need an LMS to track completion and score. Which publish format should you use?

Question 2: What's the honest truth about what your learners need to take your published course?

πŸŽ“ Course Wrap-Up β€” Look How Far You've Come

Twenty-four lessons ago, "Adobe Captivate" might have been just a name in a job listing. Look at everything you can do now:

graph TD A["🧭 Foundations
two Captivates, the honest
subscription, design thinking"] --> B["⚑ Build fast
responsive courses from
components in the all-new tool"] B --> C["🎬 Simulate & assess
screen sims, quizzes,
accessibility, publishing"] C --> D["πŸ—‚οΈ Classic survey
timeline, fluid boxes,
variables, VR/360"] D --> E["πŸ€– AI & workflow
honest AI, review,
versioning, handoff"] E --> F["πŸš€ Capstone
you planned, built &
published a real course"] style A fill:#bfdbfe,color:#1e293b style B fill:#bbf7d0,color:#1e293b style C fill:#fde68a,color:#1e293b style D fill:#fed7aa,color:#1e293b style E fill:#c7d2fe,color:#1e293b style F fill:#bbf7d0,color:#1e293b

Figure 3 β€” The whole journey, in one picture: from foundations to a published capstone course.

You learned the honest shape of Captivate β€” two products, one subscription, the all-new Adobe Captivate All-New as your modern default and Captivate Classic for its deep specialties. You built responsive courses out of components, mastered Captivate's signature screen recording and software simulation, wrote real assessments, made your work accessible, and published to an LMS. You surveyed Classic so an inherited project will never leave you stranded, looked at AI with clear eyes about what it does and what it costs Add-on / Metered, and ran a professional review-and-handoff workflow. And it all works the same on Windows and Mac Win + Mac.

πŸ’Ό A portfolio nudge

That capstone you just published isn't only a learning exercise β€” it's a portfolio piece. "Captivate" appears constantly in instructional-design and L&D job listings, and a real, hosted course you can link to says more than any line on a rΓ©sumΓ©. Keep the link handy. Build a second small course on a different kind of topic, and you've got a body of work.

🌱 Where to Go Next

The best way to keep these skills is to keep building. A few honest directions:

  • Build another course β€” a different topic, ideally one that uses a feature you didn't in the capstone (a software simulation if you skipped it, or a branching interaction). Repetition is how this becomes second nature.
  • Go deeper where you're curious β€” richer interactions, Classic's variables and conditional actions for branching and personalization, or interactive video. You now have the map; explore the corners that interest you.
  • Join the community β€” the Adobe eLearning Community is full of authors sharing work, tips, and feedback. Learning alongside others keeps you moving.
  • Learn Captivate's sibling β€” the other giant in this field is Articulate. Knowing both makes you far more employable, and the instructional-design thinking transfers directly. Ray's Articulate 360 course is a natural next step β€” build e-learning with Rise and Storyline.
  • Explore more free courses β€” Ray's House of Fun has the full library, all free, all in this same friendly style.

πŸ““ Learning Journal

Start your Learning Journal today β€” a note in your favorite app, a doc, or a paper notebook. It's where you turn "I read that" into "I can do that." After each lesson, jot down:

  • Key concepts you learned
  • Things that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and how you feel about learning this

✍️ This lesson's prompt (a final reflection): Scroll back to your very first journal entry from Lesson 1 β€” the "why" you wrote and the course you hoped to build. Did you build it? What are you proudest of, what fought you the hardest, and what's the very next course you want to make? Then write down one thing you now know you can do that felt impossible 24 lessons ago. Keep this entry. It's proof.

πŸ“ Lesson Summary

πŸŽ“ Key Takeaways

  • You author in Captivate and publish out: HTML5 for the web, SCORM/xAPI for a tracking LMS. Publish your capstone as both.
  • Test before you ship β€” click through the HTML5 output and run the SCORM package through a generic SCORM tester before it reaches a real learner.
  • Upload SCORM to an LMS and verify tracking (completion, score, pass/fail), or host HTML5 for a shareable portfolio link. Learners never need a subscription Win + Mac.
  • You've completed the full pipeline β€” plan, build, publish, test, share β€” and made a real course. That's a portfolio piece and a genuine career skill.

πŸŽ‰ What You've Accomplished

You started this course unsure what Captivate even was. You're finishing it having planned, built, and published a complete, responsive, interactive, accessible course β€” tested and shared. Along the way you learned both Captivates, Captivate's signature simulations, real assessment, accessibility, publishing, a professional workflow, and an honest view of AI. That's not "I watched some tutorials." That's authorship. Be proud of it.

❓ Common Questions at This Stage

I don't have an LMS. Did I really finish the capstone?

Absolutely. Publish HTML5 and host it for a live, shareable link, and use a free SCORM testing service to confirm your SCORM build tracks correctly. That covers both halves β€” a live course and proven tracking β€” without owning an LMS. Your capstone is complete and portfolio-ready.

My course isn't as polished as the examples. Is that okay?

More than okay β€” it's expected, and it's how everyone starts. A finished, honest, working course beats a perfect imaginary one every time. Each course you build will be cleaner than the last. The skill you just proved is that you can take an idea all the way to a published, tracked reality. Polish comes with reps.

What should I actually build next?

Another small course β€” ideally one that stretches a muscle you didn't use in the capstone (a software simulation, a branching interaction, interactive video). Then consider learning Captivate's sibling, Articulate, to round out your toolkit. Two tools plus solid instructional-design thinking makes you genuinely versatile.

πŸ”­ Where to Go Next

There's no Lesson 25 β€” you've reached the end of the path, and you've built a real course to show for it. To keep growing: build another course, go deeper into the features that intrigue you, and join the Adobe eLearning Community. When you're ready to learn Captivate's closest sibling, Ray's Articulate 360 course is the natural companion. And the whole free library lives at Ray's House of Fun. Thank you for spending this journey here β€” now go build something that teaches someone.

βœ… Before You Go

  • Save the link to your published capstone somewhere safe β€” it's a portfolio piece
  • Write your final journal reflection and compare it to your Lesson 1 entry
  • Pick your next small course topic while the momentum is fresh

πŸ“š Additional Resources

🌟 Encouragement for the Journey

You did the whole thing β€” start to finish, blank screen to published course. That takes real persistence, and you had it. Whatever you build next, you're no longer someone learning Captivate; you're a course author who happens to keep getting better. Go make something that helps someone learn. We can't wait to see it. πŸŽ“