Tuesday, August 10, 2010

Documentation ch-ch-changes

Last year we began a process of changing the way we manage our documentation. Since 1998 we had used Adobe Framemaker to produce the documentation. This was limiting because it basically only allowed one person to make changes. After evaluating many possible solutions we decided that using a wiki made the most sense.

One advantage to using a wiki is that it tracks every change we make. If you'd like to keep up with those changes, you can do so by visiting the Recent Changes page on the wiki. On that page you can also get the RSS and Atom links if you want to subscribe to a feed of the changes.

Should you find anything that you believe is an error or omission in the documentation, the best way to let us know is to file a case using Feedback.


Anonymous said...

..Turn and face the strain

Anonymous said...

Using Feedback is not always helpful. I posted there that a documentation for the database class is missing. Tho documents for the different database backends are only describing the difference to tha basic class whose events, methods and properties are not descibed anymore. The answer I got was "This is OK, is designed like that..."
Where can I get information about the database class?

Geoff Perlman said...

Can you post the case ID so we can take a look at it?