API Documentation

[Netzvamp]

Hugo is nice, but it is missing some autodoc feature like in sphinx, where the documentation is generated from the docstings in the code. When the API is growing it would be much easier to just write nice docstrings and not to maintain some separate markdown files in hugo.

[Otoru]

I don't like the experience that these document automation tools provide. The documentation process needs to be something truly designed with the user in mind. We can evolve some sessions in that direction, but I don't see us abandoning handcrafted documentation in the project.

[Netzvamp]

There can be both with sphinx. Totally unrelated to genesis, but i've made this with sphinx: https://miney.readthedocs.io
Sometimes you need just to see whats available in a class.

[Otoru]

I've used this tool and others like it, and I really don't like them. I'll keep the project in the current system, but I'm open to automations that bring value to this automation path.