Shawn Patrick Rice

Isn't that what we already have? [Here's the current build of the bundler documentation](https://shawnrice.github.io/bundler-docs/). The "quickstart" seems to be the general, language specific implementation, and the "documentation" is the auto-generated...

So, for the auto-generated sets: - AppleScript doesn't exist. - Bash had to be done by hand (and has been). - PHP is generated by ApiGen. - Ruby is generated...

The docs are just written by hand and built on Foundation 5 (similar to Bootstrap, but I like it better). Do we need more of a quickstart than the quickstarts...

And, yes, it was just too hard to get a single doc generator to generate all, so I just picked them per language and used a decent theme, but that's...

The part of automatic updates in the background should be and is (untested) part of the bundler. One problem with having the bundler is that you might install a workflow...

Two approaches: 1. Delete anything orphaned 2. Leave everything so that future workflows don't need to download it. The second needs manual intervention to happen in order to delete anything....

I've written that code a couple of times for PHP too. But go for it in Python. But, to fork it, just call the script from `update-wrapper.sh` with the same...

Okay. PHP is supposed to have [forking technology built into it](http://php.net/manual/en/function.pcntl-fork.php), but Apple decided to exclude that set of functions at compile time. I had somewhat assumed that they had...

The page also has ugly formatting. Right now, I just did a sort of content dump to get the information up there. Again, feel free to edit anything; after all,...

Well, especially with newer features, the documentation is lacking, and so it's been stuff that we've had to figure out on our own, and so the best source comes from...