So, what am I looking at? It seems like you fed the audio in PocketSphinx to get time-tagged text and the site basically shows said text as subtitles to what was said, is that the gist of it?
I actually do use markdown for the git-repo based prototype. My personal website itself actually uses that prototype. You can see an example "page" here: https://github.com/housejeffries-pages/2
Thanks for the nice words about Son. I need to get it completed (the spec still needs some touch ups) and get prototype implementations written, once that's done I think it will be pretty useful.
Thanks for the tip about StrongLink, that's definitely up my alley. Already I'm finding it useful, for instance in the docs it mentions ni URLs (https://tools.ietf.org/html/rfc6920), which is something I'd never heard of before.
If you have any more comments or criticisms of my projects feel free to email me, none of them are quite to the stage I can start promoting them yet, but getting feedback is still super important.
> If you have any more comments or criticisms of my projects feel free to email me...
Done ;-)
A first wiki could be around your project. It can be made with existing tools (pandoc, github...) if the workflow is clear enough (even with manual parts).
For example, it's possible to gather some metrics of the usage of libraries from a running process (with strace, google perftools, source maps in javascript...).
It can be a process used by a real user or autotests from the project.
A software could monitor those probes and allow the user to reward the dependencies that:
https://www.freecodecamp.com/