Thanks, that's the way I also imagined it, jsut like we do for our perl stuff.
On Feb 9, 3:03 pm, "the_woodsman" <[EMAIL PROTECTED]> wrote: > Our setup: > > We use PHPDoc for generating our documentation, which is automated and > refreshes the output nightly, and we link to these in the project's > wiki. > > Generally, we keep the PHPDoc for low level stuff (classes, methods, > members, etc) use the WIki for high level documentation (how classes > work together, sequence of method calls, etc). > > Hope that helps. > > Wood > > On Feb 9, 1:07 pm, "c1sc0" <[EMAIL PROTECTED]> wrote: > > > Hi bakers, > > > As good agile developers we're trying to automate testing, building & > > documenting our cake applications. I'm stumbling into a couple of > > questions: > > > * Developer Documentation > > ** What is cakephp using to build the 'API' documentation? phpdoc? > > ** Anyone care to comment on how they maintain (developer) > > documentation in their projects? > > > * End User Documentation > > ** Currently our approach is to build a wiki page for each project, is > > this a valid approach? > > ** What about integrating e.g. dokuwiki (www.splitbrain.org/projects/ > > dokuwiki ) in cakephp? > > > Cheers - Francis Dierick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
