Re: pyblosxom.sourceforge.net

Bill Mill <[email protected]>
Newsgroups gmane.comp.web.pyblosxom.devel
Message-ID <[email protected]>
On Thu, 9 Dec 2004 09:53:55 -0600 (CST), will guaraldi
<[email protected]> wrote:
> On Thu, 9 Dec 2004, Blake Winton wrote:
> >
> > What do you think about putting the development site at
> > http://pyblosxom.sourceforge.net/developers/, and leaving the more
> > user-level stuff for http://pyblosxom.sourceforge.net/ so that we can
> > present a friendlier face to new users?
> 
> PyBlosxom shares a lot in common with another project I worked on called
> Lyntin.  Lyntin went through several iterations of web-site organization
> and now has what you see at http://lyntin.sourceforge.net/ .  The users of
> both projects aren't "just users" because both projects water down to
> frameworks.  Users are expected to configure their PyBlosxom instances to
> meet their needs.  This often involves configuration and possibly creation
> or modification of existing plugins.  It also involves tinkering with
> templates.
> 
> I was thinking of organizing the PyBlosxom site in a similar way, though
> the categories would be "PyBlosxom", "Using PyBlosxom", and "Hacking
> PyBlosxom".  With links to the various things from there.
> 

I like it, as long as we make sure that we have a good "What's
pyblosxom?" section at the top with links to documentation and
download.

I'd be glad to help out with the web page if you'd like me to. I like
what you've got planned for it, sounds good to me.

Peace
Bill Mill
bill.mill at gmail.com


-------------------------------------------------------
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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.