First, can we give Jade commit rights to acs-core-docs?
Second, could somebody look at docs/openacs-HEAD and figure out why comments don't show up, even though I added the pages to static-pages?
Third, dribbling this thread forward:
This is of course the big ongoing discussion. In brief, my preference
is:
1) keep using docbook in cvs. (With nxml-mode in emacs, DocBook is now, barely, usable)
1a) when we ship 5.0, update openacs.org static pages so that comments work again
2) when we have a comprehensively better solution, switch
A better solution would satisfy:
a) Documents which are 'blessed' by the core team are clearly
marked
b) anybody can contribute a comment any time they are looking at
documentation, whether it's a local copy or whatever, and all of
those contributions are available to everybody else
c) both comments and documentation are associated with particular
versions (database version, oracle vs postgres, on windows vs on
mac), and browsing the documentation can be controlled by version.
(eg, show me core documentation for install, in the right sequence,
for OpenACS on red hat 9, in german if possible)
d) We can construct arbitrary paths through the documentation, such
as "Quick Install" and "Complete production install" and
"dotlrn"
e) create a printable document
Our current system, when fixed, satisfies a, partially satisfies b,
could satisfy e, and could satisfy d.
I see the new system as a combination of a new CMS on OpenACS,
categorization, and an as-yet-undefined mechanism to get local data
routed through openacs.
