Re: [Pyblosxom-devel] pyblosxom 1.5 sprint week: status (saturday)

[seanh <sn...@gm...>]

> Weird.  I really thought there was a contact page on the web-site in the
> sidebar, but it's not there.

There is a 'mailing lists' link in the sidebar, it links to a page
titled 'Contact Us' with links to the lists and bug tracker. The link
should be renamed to "Contact Us" perhaps with "Mailing lists,
IRC channel, issue tracker" as subtitle or tooltip.

But the website _should not_ have its own contact page! Since there is
already a contact page in the docs, and there is an online copy of the
docs on the website, the 'Contact Us' link on the website front page
should just link directly to the Contact Us page in the online copy of
the documentation. Don't duplicate information. Things will be much
easier to navigate if there is just one place to go to for each piece of
info, and if there are multiple copies then they will get out of sync
and then people will not know which is right.

Duplication of content between the website and the documentation has
been bothering me. I think the solution is to move information into the
docs and to put links on the website front page to particular pages in
the docs. That way the info is both on the website and in the pyblosxom
download, yet there is only one copy of it to maintain and for users to
read.

Another example of this is the "What is PyBlosxom?" page of the website
and the "About PyBlosxom" page in the docs. They contain two different
but overlapping answers to the same question. Delete the web page, and
link to the section in the docs instead.

I think the website could become merely a blog (the "news" page)
without any static pages of its own. It should have links in the sidebar
to certain pages in the online copy of the docs (contact, about
pyblosxom), to the issue tracker, and when it exists to the wiki and
certain pages of the wiki (the list of pyblosxom users and the flavour
and plugin registries should be moved to the wiki).

I'm not sure that the references/specs and colophon pages are worth
keeping. Perhaps they should be moved to the wiki also.

The development howto page belongs in the documentation.

Keep the git repositories link of course, but move it under the Download
heading in the sidebar alongside the tar.gz link(s).

At the top of the sidebar there should be a link titled 'PyBlosxom' or
'Home' or something that links back to the front page of the site.
Replace the 'Contents' title.

> 
> There's a bit in the PyBlosxom documentation:
> 
> http://pyblosxom.bluesock.org/1.5/about_pyblosxom.html#project-details-contact-information-and-where-to-go-for-help
> 
> I'll grab your paragraph plus those bits and throw together a contact page.
> 
> What else is missing?
> 
> Also, on a related note, what other projects have good web-sites that we
> could emulate?
> 
> 
> On 03/13/2011 04:11 AM, Sebastian Spaeth wrote:
> > On Sat, 12 Mar 2011 23:04:55 -0500, will kahn-greene <wi...@bl...> wrote:
> >> I'm really psyched to see things happening in the issue tracker.  I've
> >> been doing A/V work and haven't had time to do PyBlosxom work.  However,
> >> I met another PyBlosxom user here and he's interested in doing 1.5 work
> >> on Monday.  Thus, I'm planning to do a bunch of PyBlosxom work then.
> >>
> >> One of the things I'm going to tackle on Monday is the web-site.  It
> >> sucks.  It should be way better.  At a bare minimum, it shouldn't be so
> >> horribly wrong about everything.
> > 
> > One thing I was searching for lately, is the IRC channel of
> > pyblosxom. This might be good info eg on the Mailling list
> > page. Something like:
> > 
> > If you prefer more direct communication, there are often some people
> > hanging out on the IRC channel #pyb...@ch.... However,
> > sometimes no one is listening or reading the channel for hours, so if
> > you come over to say hello, be patient.
> > 
> > would already help. Thanks :)
> > Sebastian
> 
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyb...@li...
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel