Support

Find answers. Keep building.

Use the product help for everyday authoring questions, explore the developer references for custom courseware, or contact Logicdriven when you need a hand.

Documentation

Developer references

Technical documentation for extending Impression and building custom learner experiences with the same structured lesson content authored in Scribe.

JavaScript framework

BCF 2.0 Reference

Explore the Base Class Framework used by Impression Courseware Engines, including persistence, lesson and Storyboard data, events, media, canvas behavior, players, and simulation interfaces.

Open the BCF 2.0 reference →

Integration API

Impression Connect SDK

Connect external web or desktop applications to the active Impression project. The SDK reference covers the Content, Talk, and Utilities APIs used to exchange data and coordinate application behavior.

Open the Connect SDK reference →

Developer SDKs

Build on the Impression platform.

Connect specialized applications to Scribe with the free Connect SDK. For advanced development, source developer kits let teams build a custom Courseware Engine or integrate Unity simulations at the source level; most teams never need them.

Available

Impression Connect SDK

Build custom web or desktop applications that work with the active project, lesson, and Storyboard in Scribe through the Content, Talk, and Utilities APIs.

The developer kits are licensed separately for advanced development. Impression Scribe, the standard Courseware Engine, and the Connect SDK cover authoring, customization, publishing, and Scribe extensions without them. Find out whether you need one.

Product help

Guidance is built into Scribe.

Impression Scribe includes its complete authoring help with the application, so instructions remain available while you work. Open Help from Scribe whenever you need guidance on projects, lessons, Storyboards, media, publishing, SCORM and xAPI, or application settings.

The Getting Started lesson installed with Scribe provides a hands-on introduction inside the authoring tool.

Still need help?

Tell us what you were doing, what you expected, and what happened. Screenshots, error messages, and log files are especially useful for technical issues.