[mchusma]

I do like the concept, and we have struggled internally to document things. I am interested in it but the biggest thing missing for me is documentation. I can't really tell how to do it, so for me I am not really willing to try and connect and just figure out.

I do wish you luck and I think you are in the ballpark of something good here.

[Kesava1312]

Hi! Sorry we did not have a better CTA. Here's a one-minute form to help you get onboard: https://bit.ly/3aoFAZO

There's actually no need for documentation - we have a one-click integration to Github, where you'll click the repo and the documentation gets auto-generated. Excited to let you try it!

[solidasparagus]

There is very much a need for documentation. I keep hearing "auto-generated" documentation, but I don't see what differentiates this from other tools that generate docs from code comments. Without more detailed information about what this tool does, there is no reason to pursue it further.

There are myriad questions that need answering with docs:

- What does autogenerating documentation mean? (in my book, exposing code comments is not autogeneration so hopefully there is more)

- When I edit function documentation does it also change the code comments? Vice versa?

- How is the documentation version controlled?

- How are multiple versions of a library documented?

- What level of customization do I get? Just look at the Sphinx ecosystem for all of the things that people end up needing to customize.

- The chore part of documentation is thinking about what to write and writing it so that it is easy to understand - does this actually help me here?