Advanced Help/Documentation System For Linux

[josh]

For type usage in general, I favor

incremental refinement – ala Typescript – add extra typing to the universal type as it becomes helpful to what you are trying to do. In this documentation world, lots of arguments, for example, are “readable file”. In many cases, the requirement is much more specific than that, but it may not be helpful to spend time creating 1 off types for many apps. Add the extra bits when it’s helpful.

multiple views of the source format – this is my personal view – more typing info is often helpful, but the help should not come at the cost of a cluttered view with information overload. The view should default to clean uncluttered views in a presentation system where it is ez to access the additional info if it is desired – e.g. click on the file object to get a popup or switch the view to 1 that includes more detailed info.

[josh]

The Common Workflow Language appears to be something of an academic boondoggle without great use cases. But it is, or was, a funded boondoggle, that shows an example of funding & creates an edge for more advancement. Thinking about that motivates the suggestion that hidden partnerships with academics is another area worthy of GT exploration. Many academics are good matches to the profile of figure-head public collaborator who would be happy to jump & happy to covertly represent. Once funded, they have a lot of discretion over the $$$ flows. I say “examine that explictly as a new search category”.

[Author]

Posts