Anton Vishnyak

@ericholiveira Fantastic ideas on both fronts. I was going to suggest 2 myself. In fact, I would love to take that one on because I have a ton of ideas...

Regarding wrappers, I think we would fall into the Seneca trap there where you have a ton of half-baked, buggy wrappers with no maintainers which will give the overall framework...

I think some of the things there can be enforced using [issue and PR templates](https://github.com/blog/2111-issue-and-pull-request-templates).

I tend to use [DocStrap](https://github.com/docstrap/docstrap) (a JSDoc3-based doc generator) because it's easy to get running, everyone understands [JSDoc](http://usejsdoc.org), is themeable, has search built in and has the ability to add...

@ericholiveira we can probably make jsdoc to gitbook happen by using [jsdoc-to-markdown](https://www.npmjs.com/package/jsdoc-to-markdown) as part of the build steps. Also, here is an example of what looks like gitbook documentation that...

I have run into this issue as well. The slowness is coming from the `git subtree split` command that is used whenever you provide an `appdir`. This runs through every...

The ui-router feature allows a child route to fill in slots on a parent route. Adding the views field to Route makes sense to me. I think the first feature...

I'll help with it when we decide on the gitbook & jsodc solution... that way we can roll the documentation together into a real gitbook that's comprehensive later on.