I also like to setup a plugin library on github. You can look at https://github.com/mklauber/tw5-plugins to see how I'm making http://mklauber.github.io/tw5-plugins/. The important part is https://github.com/mklauber/tw5-plugins/tree/master/plugins/mklauber Each of my plugin repos are sub repositories of the plugin library repo. https://github.com/mklauber/tw5-plugins/blob/master/publish.sh is a bash script that pulls in updates, builds a new .html file, commits it to the gh-pages page, and then pushes that. So I can version control all my plugins separately, and distribute them in one place. I haven't gone this far, but it would be possible to setup travis-ci to rebuild the plugin library whenever one of the plugins is updated.
Matt Lauber On Wednesday, January 18, 2017 at 5:30:23 PM UTC-5, Jed Carty wrote: > > Is it useful to have tiddlywiki html files with plugins on GitHub? I have > links to the demo sites so it may be redundant but I am not sure how other > people feel about it. > > I am moving a lot of my tiddlywiki things onto GitHub as OokTech since I > am working as OokTech now. I am hoping to clean up the code and improve > documentatino while I am doing it so this is going to be part of that. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/6f5691d3-90d0-4ae7-a446-84b2a79d5f9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
