jeff-optimizely/Guiders-JS — pull request #77 by tychay (2012-11-30 22:51:27+00:00)
Title: Guiders to work across page loads (and other changes)

This is some stuff that I wrote a year ago that WordPress used for Guided Tours on WordPress.com. The main change was some extra functionality to allow the tour to work across multiple differing pages which necessitated some changes like
* a cookie to allow guiders to be continued even if a UX element were clicked
* a way to auto-advance the guider when an event occurs instead of the guider being clicked
* a way for a tour to be loaded without error, even if the UX element a guide can be attached to doesn't exist yet/in that page
… etc.

These do not break/change existing functionality in Guiders.js (as of August 2012)

That went live on WordPress back in 2010, but I was also planning on making this available as a plugin for WordPress.org installations which I never finished.

Wikipedia plans on using doing a [Guided Tour](https://www.mediawiki.org/wiki/Guided_tours) as part of [Onboarding experimentation](https://www.mediawiki.org/wiki/Onboarding_new_Wikipedians) and in the process, Guiders might get [modified a lot](https://gerrit.wikimedia.org/r/#/c/35399/)--plus it would make sense to have a way to upstream those changes.

I updated Guiders a couple months ago to track your changes in the last year and a half, so the js files, at least, should merge cleanly.

Note that there is some stuff related to the wordpress.org plugin I never finished (things like wp-guiders.css and some notes in the README) if you merge the pull, feel free to delete them. If I ever redo guiders for WordPress, I'll just do it via Git submodule :-)

Take care,

terry