[tw5] Re: TiddlyWiki as a target for generated help documentation
I have started to look at the command-line available in node, and it seems like once I have all my pages in a single appropriate json file, then what I could do for my prototype is simply all a single line somewhere near the end of my build script: tiddlywiki ./DataDictionary --init empty --import allmydata.json --rendertiddler $:/plugins/tiddlywiki/tiddlyweb/save/offline index.html text/plain Then I have it all in a single file I can send someone to play with. And that looks like a good start. Thanks, Cade On Saturday, August 10, 2019 at 12:22:13 AM UTC-5, TonyM wrote: > > Cade, > > Others have used tiddlywiki to consolidate documentation in the past. > Using csv or JSON has the most tools and features available in 3rd party > plugins. Import and export, so these may be good standards around to build > data interchange. > > I can't grasp the whole of your requirements but much of it touches on > things I have done or researched. Do consider opening threads here in the > forum with a specific or subset of things you are trying to do do so people > do not need to understand your whole project to help. It is easier for > people to volunteer for issues rather than projects, although it is great > you have outlined the bigger picture here. > > How you are going to access and host your wiki can have an influence here. > The node version also publishes every tiddler as a separate "static" html > page, and you can export any tiddler as static html even from a single file > wiki. Crafting of additional templates like those to export static html > pages could be used to export html pages to build a standard html site, > however as Mat suggested it would be in your interest to keep as much as > practical in one tiddlywiki because of the control and global handling you > can do. > > Perhaps in the recent 5.1.20 release post you can see my comments on the > Innerwiki Plugin, not that I am sure this will help with your project. With > tiddlywiki the sky was the limit now I think it is the stars. > > Regards > Tony > > > On Saturday, August 10, 2019 at 7:54:24 AM UTC+10, Cade Roux wrote: >> >> Yeah, I have a large amount of metadata that is changing, and the source >> of that data is either going to be: >> >> 1. Originating in the metadata of the SQL tables (attached to the tables >> and columns) - kind of basic data dictionary things which will look like: >> >> > /> >> >> Where we would want to generate a page for every one of these >> automatically from the source code (mostly manually edited) during the >> build. There might be also editable narratives to go with them. >> >> 2. It is going to be in rules that original in Excel (manually edited), >> go through XML and then become data in mapping tables. >> >> These are kind of similar, but have much more data about the source data >> that matches the rule and the output data, plus the edited narratives are >> more likely to include screenshots and longer explanations. >> > /> >> >> >> 3. Other things: Perhaps pages of build results like any warnings, >> exceptions or errors in the rulesets in the current build process that we >> detected from #2. Technically we already get these as logs or tables, but >> makes sense to include them in the set of pages if we have an HTML >> framework to put them in now. >> >> It's unlikely I want to put TiddlyWiki on the front end of this process >> because I do need to check in structural changes like new tables, columns, >> views and procedures with their metadata all together. Plus I don't think >> generating all my SQL from TiddlyWiki pages makes a lot of sense. Plus, I >> would need to transition writing the rules from a spreadsheet to TiddlyWiki >> Tables - and we do occasionally use Excel macros to make these more >> functional for data input and validation. >> >> There are two obvious approaches: One is to generate the page framework >> from all the data we have and incorporate manually edited data somehow - >> like another manually edited source. The other is to have manual set of >> pages which can embed automatically generated content as some kind of >> widgets or plugins of the form > Category='CategoryName' DataElement='DataElementName' /> or whatever >> >> There currently isn't any web-based application built that is hitting >> this data warehouse. If I had that I could make some kind of service to >> serve up the metadata and plug it into manual pages as a widget or plugin. >> I could also just build an app that lets you navigate the metadata and >> allows annotation and stores it somewhere and displays it all to the user. >> But I didn't really want to build an app yet until we've explored the gaps >> in the data and the features people will need. >> >> I could just going to generate a bunch of HTML pages with links. But I >> would have to style them, have some framework, navigation, etc. Again, not >> ready to build all that just yet - just
[tw5] Re: TiddlyWiki as a target for generated help documentation
Cade, Others have used tiddlywiki to consolidate documentation in the past. Using csv or JSON has the most tools and features available in 3rd party plugins. Import and export, so these may be good standards around to build data interchange. I can't grasp the whole of your requirements but much of it touches on things I have done or researched. Do consider opening threads here in the forum with a specific or subset of things you are trying to do do so people do not need to understand your whole project to help. It is easier for people to volunteer for issues rather than projects, although it is great you have outlined the bigger picture here. How you are going to access and host your wiki can have an influence here. The node version also publishes every tiddler as a separate "static" html page, and you can export any tiddler as static html even from a single file wiki. Crafting of additional templates like those to export static html pages could be used to export html pages to build a standard html site, however as Mat suggested it would be in your interest to keep as much as practical in one tiddlywiki because of the control and global handling you can do. Perhaps in the recent 5.1.20 release post you can see my comments on the Innerwiki Plugin, not that I am sure this will help with your project. With tiddlywiki the sky was the limit now I think it is the stars. Regards Tony On Saturday, August 10, 2019 at 7:54:24 AM UTC+10, Cade Roux wrote: > > Yeah, I have a large amount of metadata that is changing, and the source > of that data is either going to be: > > 1. Originating in the metadata of the SQL tables (attached to the tables > and columns) - kind of basic data dictionary things which will look like: > > /> > > Where we would want to generate a page for every one of these > automatically from the source code (mostly manually edited) during the > build. There might be also editable narratives to go with them. > > 2. It is going to be in rules that original in Excel (manually edited), go > through XML and then become data in mapping tables. > > These are kind of similar, but have much more data about the source data > that matches the rule and the output data, plus the edited narratives are > more likely to include screenshots and longer explanations. > /> > > > 3. Other things: Perhaps pages of build results like any warnings, > exceptions or errors in the rulesets in the current build process that we > detected from #2. Technically we already get these as logs or tables, but > makes sense to include them in the set of pages if we have an HTML > framework to put them in now. > > It's unlikely I want to put TiddlyWiki on the front end of this process > because I do need to check in structural changes like new tables, columns, > views and procedures with their metadata all together. Plus I don't think > generating all my SQL from TiddlyWiki pages makes a lot of sense. Plus, I > would need to transition writing the rules from a spreadsheet to TiddlyWiki > Tables - and we do occasionally use Excel macros to make these more > functional for data input and validation. > > There are two obvious approaches: One is to generate the page framework > from all the data we have and incorporate manually edited data somehow - > like another manually edited source. The other is to have manual set of > pages which can embed automatically generated content as some kind of > widgets or plugins of the form Category='CategoryName' DataElement='DataElementName' /> or whatever > > There currently isn't any web-based application built that is hitting this > data warehouse. If I had that I could make some kind of service to serve > up the metadata and plug it into manual pages as a widget or plugin. I > could also just build an app that lets you navigate the metadata and allows > annotation and stores it somewhere and displays it all to the user. But I > didn't really want to build an app yet until we've explored the gaps in the > data and the features people will need. > > I could just going to generate a bunch of HTML pages with links. But I > would have to style them, have some framework, navigation, etc. Again, not > ready to build all that just yet - just looking to output something people > can interact with and tell me what's missing so we can get it added > somewhere in the process. > > Basically, anything where I can load a big file like name="Home">wiki markup herewiki markup > herewiki markup here would be > great. > > In fact, that's basically what I am starting to generate for whatever > presentation layer we end up using. > > So I was looking to potentially push out a pre-built TiddlyWiki at the end > of this process right now so people can browse it and see where the gaps > are and what they would like to see. I think ideally it would probably > morph into something where they could edit any of the discussions or > narratives and
[tw5] Re: TiddlyWiki as a target for generated help documentation
Yeah, I have a large amount of metadata that is changing, and the source of that data is either going to be: 1. Originating in the metadata of the SQL tables (attached to the tables and columns) - kind of basic data dictionary things which will look like: Where we would want to generate a page for every one of these automatically from the source code (mostly manually edited) during the build. There might be also editable narratives to go with them. 2. It is going to be in rules that original in Excel (manually edited), go through XML and then become data in mapping tables. These are kind of similar, but have much more data about the source data that matches the rule and the output data, plus the edited narratives are more likely to include screenshots and longer explanations. 3. Other things: Perhaps pages of build results like any warnings, exceptions or errors in the rulesets in the current build process that we detected from #2. Technically we already get these as logs or tables, but makes sense to include them in the set of pages if we have an HTML framework to put them in now. It's unlikely I want to put TiddlyWiki on the front end of this process because I do need to check in structural changes like new tables, columns, views and procedures with their metadata all together. Plus I don't think generating all my SQL from TiddlyWiki pages makes a lot of sense. Plus, I would need to transition writing the rules from a spreadsheet to TiddlyWiki Tables - and we do occasionally use Excel macros to make these more functional for data input and validation. There are two obvious approaches: One is to generate the page framework from all the data we have and incorporate manually edited data somehow - like another manually edited source. The other is to have manual set of pages which can embed automatically generated content as some kind of widgets or plugins of the form or whatever There currently isn't any web-based application built that is hitting this data warehouse. If I had that I could make some kind of service to serve up the metadata and plug it into manual pages as a widget or plugin. I could also just build an app that lets you navigate the metadata and allows annotation and stores it somewhere and displays it all to the user. But I didn't really want to build an app yet until we've explored the gaps in the data and the features people will need. I could just going to generate a bunch of HTML pages with links. But I would have to style them, have some framework, navigation, etc. Again, not ready to build all that just yet - just looking to output something people can interact with and tell me what's missing so we can get it added somewhere in the process. Basically, anything where I can load a big file like wiki markup herewiki markup herewiki markup here would be great. In fact, that's basically what I am starting to generate for whatever presentation layer we end up using. So I was looking to potentially push out a pre-built TiddlyWiki at the end of this process right now so people can browse it and see where the gaps are and what they would like to see. I think ideally it would probably morph into something where they could edit any of the discussions or narratives and have that change recorded and save and potentially fed back through some change management process. Who knows, maybe TiddlyWiki is the perfect platform for the whole thing with some kind of plugin. Thanks, Cade On Friday, August 9, 2019 at 3:51:35 PM UTC-5, Mat wrote: > > Hi Cade and welcome! > > Reading your text I was thinking "OK, that is super simple" ...until you > said > > So is there a way to generate a set of pages or the content for the pages >> and have them "loaded" into TiddlyWiki? >> > > Oh. That is a different matter. Someone just very recently posted > something about this (within the last month) but the crucial thing is if > you want your content to be actively integrated in TW or not. Now you state > you have not quite defined what you want so may I suggest that you just do > it all in TiddlyWiki? You can very easily export tiddlers as e.g ready made > html pages or as e.g json files. Or just leave it in the TW because it is a > single file which you can manage as a unit. > > Would that work? > > I suggest you play around a bit with TW to see how it works so you can > express your needs more in "TW terms". > > <:-) > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/dee7d202-dede-475b-a3e5-99a1ca2fb5ca%40googlegroups.com.
[tw5] Re: TiddlyWiki as a target for generated help documentation
Hi Cade and welcome! Reading your text I was thinking "OK, that is super simple" ...until you said So is there a way to generate a set of pages or the content for the pages > and have them "loaded" into TiddlyWiki? > Oh. That is a different matter. Someone just very recently posted something about this (within the last month) but the crucial thing is if you want your content to be actively integrated in TW or not. Now you state you have not quite defined what you want so may I suggest that you just do it all in TiddlyWiki? You can very easily export tiddlers as e.g ready made html pages or as e.g json files. Or just leave it in the TW because it is a single file which you can manage as a unit. Would that work? I suggest you play around a bit with TW to see how it works so you can express your needs more in "TW terms". <:-) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bf5ffc0d-767e-41a3-838b-1dd0f8c4fb5b%40googlegroups.com.
