> hyde does not produce pretty-printed output. Rather, it produces well structured Markdown files that contain YAML front-matter. These files can then be consumed by other tools (like Jekyll) to customize the structure and layout of the final documentation.
To me the readme and examples you've linked read like:
1. You write normal code with no inline documentation, and no links to external documentation.
2. You run it through a tool with produces JSON. And feed that into a static sure generator.
3. Your code is now magically documented. Somehow.
I have no idea where the actual documentation is...
I would love to see Hyde dogfood Hyde. I think that might be helpful to those coming in to check it out. What does the documentation of Hyde look like put through Hyde and output through vanilla Jekyll?
Clever name, by the way.