pyblosxom.sourceforge.net

I spent a few hours today pulling together a prototype of the "new" 
PyBlosxom site.  I did a lot of content for the site.  Silly things like 
mission statements, marketing blurbs, development guidelines, ...  :)

Anyhow, someone (or someones) should go through what I've done so far and 
either bless it or offer adjustments to the existing text.

    http://pyblosxom.souceforge.net/

Things that haven't been done yet:

1. installing xml_rpc and xml_rpc_blogger
2. installing the registry and moving all the plugins over
3. moving my documentation over

I'm tossing around installing a wiki, but I'm not sure I really want to. 
I certainly don't want to deal with what we're dealing with on Wari's 
site.

I'm thinking instead of doing that, we should do something like what 
php.net has where they have documentation that's "official" and then users 
can toss comments on it.  It sure makes it a lot easier for us to control 
what is and what isn't "official" documentation.

I realize this puts the onus on developers and people with access to the 
site to develope the documentation.  I'd like to tackle a bunch of it.  So 
I'll take that task for a while until I run out of steam and/or hit things 
I don't know how to document.

If this doesn't work out, then we can add a wiki to the site.  At this 
stage, I'd like to reduce the complexity and administration costs 
involved.

Any thoughts/comments/suggestions and such, let me know.  Also, if someone 
wants to do up a better stylesheet--please do.  I'm not wildly psyched 
about the one I threw together, but it works ok for now.

/will

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/