On 28 Dec 2005 11:17:07 -0200, Jorge Godoy <[EMAIL PROTECTED]> wrote: > > Elvelind Grandin <[EMAIL PROTECTED]> writes: > > > Yes, that a good point. The problem is that the user still needs to > > figure out if the solution to there problem is in CP, turbogears or > > some other module. > > Unified docs would solve that problem > > How are these docs written? XML? LaTeX? Using docstrings? Having them > "fixed" on CP's docs and mirroring the desired parts to TG's website seems to > be the best thing to do.
Jared and I have talked about interesting ways to generate the table of contents (or even multiple tables of contents for different audiences) for the docs section of the site. Breaking out the CherryPy docs this way seems valuable. Since they're XML, that gives us some nice options. (We've also talked about breaking up the Getting Started doc similarly... this is where it's nice that the docs are all XHTML - easy to slice and dice.) Kevni
