Mohammad you are already hosting your plugin and script directory on Github. What if we do this,
1. Break down the html into individual tiddlers and host in Github repository 2. Use Travis to build these tids into html file using tiddlywiki command. For example tiddlywiki ~/Dropbox/TiddlyNotes --verbose --build index *. If we use GitLab then using an external integration tool will not be necessary. 3. Host the generated index.html via Gitub pages And finally use this repo as the official plugin repository. Advantage of breaking down into individual tid files is 1. All tids are just text files 2. Easier to view the code and suggest changes 3. Use Github as the CMS for plugins 4. We can enforce contributors to use some standard fields in their tids like author name, url, contact email etc 5. Use Git for versioning 6. Contributors can use Github online IDE to make changes or add new tid. All their contributions will be received as PR, which maintainers can review before merging 7. Git already is being used for distributed development. TW community can certainly take advantage of it. 8. Use git tags and releases user will know which plugin has been upgraded and then they can upgrade it manually I guess bottom line of my suggestion is to use Github/GitLab repository as a official CMS for TW plugins and scripts. -- 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/b326f0c8-2041-4f41-89c6-b295d27313f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
