I wouldn’t really create different pages for each version, but keep it like MSDN: same page but you can select the .Net version and get that specific help.

I made a prioritized list of improvements you could consider below:

1. Documentation should be linked 1 to 1 with a batch/release. Like Microsoft does per .NET Framework release. So don’t add properties to an existing document with the text behind them saying: ( from batch 395 ). No, just create a document per batch.

2. I don’t know how documentation is created now but I clearly have the idea that it is done manually. This is normal if we are talking about walk-throughs etc. For object reference documentation this is a different case. I would suggest keeping the documentation closer to the code or in between the code ( XML-doc style ) so documentation can be generated. This improves the accuracy of the documentation because you do not have to keep it in-sync manually.

3. Expand the documentation. More code examples would be nice but adding some semantics/meaning to properties and methods would be even nicer! For example: The property TransShipment of object SDKSalesOrder now has the following description: Intrastat. References field trsshpm_cd in table intshp, combined with land_iso. This does not tell me for what purpose I should use this property!? It is technical blabla and hardly useful?

4. Style/markup. The way the documentation is presented is not very clear. For this I refer to Microsoft’s MSDN docs again. This does not mean you have to copy it exactly but I think you could learn from it.

I hope this is clear. if not, you no where to reach me.

Good luck!