Ok. Here's a plugin. This isn't great, but it might give someone an idea for making something better.
I think that the underlying code at the main Glider.js site depends on tricking the browser into invoking the same code multiple times. This may or may not work, depending on the browser and platform. So, the same limitations will almost certainly show up in TW.
I strongly recommend testing this only in an empty or otherwise unimportant TW. I put in error catching code, which I think reduces problems, but .... who knows whether it covers all the bases. Absolutely be sure to have backups before using this anywhere important!!
There are 3 components in making Glider(s) work:
1. HTML code with parts identified by ID or Class
2. A Query selector to find those parts
3. A JSON string to provide options for how the parts are to work together.
There is a usage tiddler ... but I feel that my powers of prose may not have been at their best.
All of the examples at the original site, and one of my included one's need FontAwesome to look right. I did not include that technology, but you can obtain it from the usual suspects.
Good luck!
-- Mark