Step by step, online help is ever more prevalent. A huge step forwarded was achieved with the Revit 2012 product WikiHelp system with its support for community building and contribution, and the Revit API documentation soon followed suit.
The Content Wrangler recently published an interesting article and interview discussing the topic in more depth.
Following up on this, here is some more detailed information and suggestions specifically targeted at the Revit API help by Mikako Harada, ADN AEC Technical Lead:
As some of you are already aware, we now have an Autodesk Revit API Developer Guide on Autodesk WikiHelp. You can access it from www.autodesk.com/revitapi-help. This is the place where you will find the latest, up-to-date Revit developer guide. Of course, Wiki means this is the place where we all can contribute and become a part of the community.
To get you motivated to look at our Revit API Developer Guide on WikiHelp, and to encourage you to start contributing, we have picked up the following two topics to share with you:
Did you know that you can create content under your own page? Every user has their own location in the WikiHelp, in which you can add pages and edit content. Here is how you can access it:
The image below shows an example of how it looks like when you go to 'Edit page' > 'Edit content' mode. You can easily figure out what each basic function does from icons.
As mentioned earlier, all users have the 'My page' location and it is intended as a public page. For example, on the landing page of the WikiHelp, you can click on any of the user names of the 'Top Contributors' to see their My page profile.
If you are not yet familiar with the WikiHelp environment, this is a good place to start playing with WikiHelp and learn how to write a page until you feel comfortable modifying the existing content.
If you are a programmer thinking about contributing to any of the Developer Guide section of WikiHelp, you will most likely find formatting in WikiHelp not as straightforward as you wish. Soon you will start wondering what the best way to add a code sample is. (In fact, that's what we struggled with when we started!)
Here is one suggestion that we want to share with you to make formatting code less painful:
At this point, the transformation you set does not have any visual effect. You will see it only after you save it and exit the edit mode.
You still lose the exact colour coding that you had in your Visual Studio IDE. But with the current functionality of WikiHelp editing, the above seems to be the easiest. We, including the Revit API team, have decided to stick to following this way from now on.
We look forward to seeing your contribution in our Revit 'API Dev Guide' section very soon.
Acknowledgement: many thanks to Elizabeth Shulok of Structural Integrators, LL C, ADN member, for her valuable feedback about editing in WikiHelp, and many thanks to Mikako for this helpful summary!