1. cherrypy
  2. CherryPy
Issue #197 resolved

Clean up Wiki

Anonymous created an issue

We should move the good content from the Wiki to the new docs.cp.org and then clean up the wiki (it would only be used by cp devs).

Reported by lawouach

Comments (19)

  1. Anonymous

    One interesting and simple way to handle that would be to add a simple 2.0 or 2.1 next to a recipe, for instance :

    How to serve static content with CherryPy (2.0, 2.1)

  2. Anonymous

    I think we need a trac macro/plugin that will automatically create a wiki page for the official documetantion. The docs should not be editable but we should us the wiki to allow comments at the bottom of the page.

  3. Anonymous

    I think is quite safe as it is now and that pages refering to 2.0 code have a mention to different behavior with 2.1 (ie link to WhatsNewIn21).

    I'm confident we can close this one.

    If some pages aren't up to date, then we'll fix them as we go.

  4. Anonymous

    It seems that a lot of TurboGears users are refering to our wiki to explain how to do basic things as well as more complicated ones. Some are refereing to the book as well.

    The problem is that most of wiki recipes are not explaining well enough how things should be done in CP 2.1, confusing people quite a lot and giving a bad image of CP.

    I think we need to do a cleanup of the wiki asap.

  5. Robert Brewer

    I've adopted a new approach to wiki pages: I'm converting them to reference the latest version, and putting notes at the bottom of the page which describe changes needed to work with previous versions. At the moment, of course, the latest verison is 3.0 beta, but I think this scheme can work as we move forward.

  6. Robert Brewer

    The following pages need to be cleaned up:

    • BasicAuthFilter and DigestAuthFilter should be removed and merged into [wiki:rfc2617]. All the other *Auth modules should be examined as well.
    • CpgRequest and CpgResponse: can we drop these altogether?
    • If the XForms page stays, it needs to be simplified, and the attachments folded into the page, so it can be upgraded to 3.0 and have a compatibility section written.
  7. Anonymous

    Removed the WForms page which would have required too much work for being relevant. I will add it one day in the future :)

    Updated rfc2617 to point at the correct files.

  8. Log in to comment