A framework to make it easy for developers to add product tours to their pages.
This project is no longer used by LinkedIn and is currently unmaintained.
Hopscotch is a framework to make it easy for developers to add product tours to their pages. Hopscotch accepts a tour JSON object as input and provides an API for the developer to control rendering the tour display and managing the tour progress.
To learn more about Hopscotch and the API, check out linkedin.github.io/hopscotch.
/archivescontains .zip and .tar.gz files of prior and current distributions of Hopscotch.
/demohas a simple demo page with a Hopscotch tour. Much of the content duplicates what's on the github.io page.
/distincludes compiled files for the current version of Hopscotch. This folder gets zipped up into an archive when a new release is published.
/testis our testing suite for the core framework, written using Jasmine.
The Hopscotch files included in
Check out linkedin.github.io/hopscotch for usage examples and a live sample tour. If you'd like to tweak some of the default assets included with Hopscotch to best suit your project's needs, read on for details about how to modify and rebuild a custom version of Hopscotch.
Hopscotch is built using Grunt.js. Learn more about how to get started with Grunt. Running
gruntwill build Hopscotch (publishing artifacts to
/tmp) and run the test suite against the newly built artifacts.
Testing is done as part of the build process using the Jasmine testing framework. You can run
grunt testto verify changes.
Continuous integration is run against every pull request using Travis CI. Please verify your changes against the test suite before submitting a pull request! We also recommend adding new tests for any new features or bugfixes as feasible.
Depending on your use case, you might want to modify and/or rebuild some of the basic components included with Hopscotch. Some moddable options include...
/src/tlfor details. Any templates in
Note: We're currently in the midst of refactoring Hopscotch into a newer module-based format that should help make readability and maintenance a lot easier. While this work is in progress, we'll be halting changes to the master branch of Hopscotch, apart from major maintenance fixes. Please feel free to continue submitting bug reports, though do keep in mind that they not be addressed in the current iteration of the library. Thanks!
See CONTRIBUTING.md for details on how to contribute back to the public Hopscotch repository on GitHub.