Some questions

[noraj]

I find yard way better than rdoc and use it for all my ruby programs and I find default crystal documentation system very basic, so that's only natural I found about crodoc.

I have several questions :

1. Does crodoc supports @param, @option, @return like Yard? (I see none in examples)
2. Could you document what are all the keywords supported?
3. Could you build crodoc documentation using crodoc and host it on github pages so we could have a live demo?
4. Does it work with Crystal 1.7?
5. Do you still plan to maintain it or should I consider it abandoned?
6. How to use it? The section is blank https://github.com/watzon/crodoc#usage, it doesn't override crystal docs it it must use it's own command.

[watzon]

This was an idea for a project more than an actual project. It is currently completely non-functional.

[noraj]

It was a good idea then 🙂

[watzon]

I would like to come back to it, it's just going to take some time. The difficulty with a project like this is that you can't rely on Crystal's built in documentation generator at all, which means you need to hook into the compiler, build an AST for the code you want to document as well as collecting all of the comments, and then build the documentation from that.