Posted by larry on 10/13/56 11:30

This idea came to me yesterday as I was working on a Web based DB for
work:

Instead of having the documentation be a hard coded page, use a wiki to
manage it, then you can update on the fly as necessary - which would
also work great for prototyping the documentation or implementation of
a more flexible on-line documentation system.

Here I've been using eWiki to do some Wikipages for work, it uses just
a single page reference with some GET data for which page to pull up.
(i.e. ewiki.php?id=FontPage) In my php app I can make my category
headings (or whatever I need documentation for to point to a wiki with

(a href="ewiki.php?id=NewClientRecord" target="_blank")How to Add a
Client Record(/a)

If the wiki page doesnt exist, ewiki puts me into an editor, if it does
it displays the page. This also gives the end-user a chance to write
the docmentation right (fixing my spelling errors, etc.) or to adjust
it over time due to updated policies and procedures.

Larry

Link:
Ekiki - http://erfurtwiki.sourceforge.net/

[Back to original message]