--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
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/32fe3015-6bdf-4fca-a51f-ab279900890e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I am part of a project that currently uses a GitHub wiki as it's main source of documentation (https://github.com/belaplatform/bela/wiki).
Since it is based on Markdown, is it possible to automagically turn it into a TiddlyWiki?
Further, would it be possible to upstream updates from the GitHub wiki?
As Jeremy pointed out. Relatively straight forward, but some tweaking needed. Since There are only 39 wiki pages atm. Manually transferring the stuff should be about 1h work.
Thanks for the replies everyone. It certainly seems doable!
@Pmario, we have not really proposed this as a definite change, and the wiki would still stay on GitHub at least for now. We are interested in options for having the wiki available in our environment though so TiddlyWiki could be a possibility for that.
The benefit that I see is that each user could then edit this base wiki to make it their own and document their projects, and potentially contribute back to the main wiki.
As I wrote, that should be possible too. ... But I'm not sure, how you would want to implement it. .. IMO for a "low latency" system, it's important, that only the stuff that's really needed is running. ... So the final workflow, will need to be discussed.