Many of you have complained in the past about the quality of the Civil 3D API documentation, and I cannot agree more with all your comments. Writing good documentation is very difficult; especially, when there is such a diverse audience with different wants and needs. It helps to understand what the main pain points are to concentrate efforts and improve the quality over time.
I need your help to understand what type of things we need to do to improve our documentation. I am sure we are doing some things right, but I would like to understand better what we are doing wrong.
If you have a few minutes, use the comments area to send me a couple of things that you will really like to see improved in the API documentation. Do we need more how-to articles? Do we need more code samples? Do we need to improve search and navigation? Anything that is causing you pain, we want to hear about it. I cannot guarantee that everything will be addressed, but we will make a big effort to address the most important things.
Thanks in advance.