Re: [tw5] Parsing other format to tiddlers: in build step or within TW?

TonyM wrote: > Alot of this is over my head, but can I suggest in your readonly view > you make use of the new comments plugin in 5.1.18 or a version of it > so than non editors can comment on any tiddler and send those comment > tiddlers to an editor. Thank you. While this wouldn't be

Re: [tw5] Parsing other format to tiddlers: in build step or within TW?

Alot of this is over my head, but can I suggest in your readonly view you make use of the new comments plugin in 5.1.18 or a version of it so than non editors can comment on any tiddler and send those comment tiddlers to an editor. Once I see the final comnent plugin I plan to build an import

Re: [tw5] Parsing other format to tiddlers: in build step or within TW?

Thanks for the great feedback! Jeremy Ruston wrote: > I’ve also been thinking about something similar: using TW5 to create > a reusable tool that interleaves documentation files in a standard > git repository, threading them together to construct a TiddlyWiki that > can be used to view/edit the

Re: [tw5] Parsing other format to tiddlers: in build step or within TW?

Hi Scott I’ve also been thinking about something similar: using TW5 to create a reusable tool that interleaves documentation files in a standard git repository, threading them together to construct a TiddlyWiki that can be used to view/edit the docs, or to generate static renderings. I think

[tw5] Parsing other format to tiddlers: in build step or within TW?

I'm working on a new programming library and want to generate a tiddlywiki version of the documentation to serve from Node. I'm looking for advice on the best way to do this. I will be maintaining the documentation in a markdown-file-per-function format; this will work well with our GitHub