Re: [Pyblosxom-devel] new site pushed

[Dieter P. <di...@pl...>]

On Fri, 18 Mar 2011 22:42:15 -0400
will kahn-greene <wi...@bl...> wrote:

> I reworked a ton of content on the web-site, removed a bunch of stuff,
> added some new things, and reorganized everything.
> 
> http://pyblosxom.bluesock.org/
> 
> There are some outstanding things that need to be done:
> 
> 1. we need to finish up changes to the documentation, then compile that
> and push it to the site -- Sean has done a ton of stuff and I haven't
> caught up with looking through those changes, yet.
> 
> 2. we need to finish up updating the plugin registry
> 
> 3. we need to finish up updating the flavour registry
> 
> 
> After that, I think the web-site is good enough to do a 1.5 release.
> After 1.5 we should talk about other things we can do to improve the
> site.  Improving the look-and-feel is probably a good thing to work on.
> 
> 
> I'd love to hear people's thoughts and whether there are other critical
> things we should improve now. 

the links "report bug" / "request feature" point to the same. why not just one link "bugtracker"
or maybe "bugs / tickets" but I think 'bugtracker' is clear to everyone that it also includes feature requests and/or misc tickets.


> 
> 1. the features list on the front page -- are there other things we
> should mention?  things we shouldn't mention?

* the last line basically repeats the 2nd point. imho remove it entirely.
* "works with blog standards" -> maybe mention this is done through templates so that people don't think the core has bloat for that built-in.
* otherwise I think this bullet list is very accurate and clear.

> 2. the quick start section on the front page -- it's slightly more
> complicated than these steps, so I wasn't sure whether to include them
> or not, but I really like the idea of having a quick start

instead of [ edit config.py ]
you could put $ $EDITOR config.py


> 3. the "how to send us a patch" section on the development page -- do
> those instructions look adequate?  how would you improve them?

* has a typo commet -> commit

* an alternative for patches is pushing commits to gitorious (or any other public git repository) and issuing a pull request (in the latter case, a pull request is basically a mail saying "please pull from that repo/branch")
looks ok otherwise.

> 4. the navigation items in the sidebar -- is it saner than it was
> before?  are there better names for some of the sections that we should use?

* you can put me on the pyblosxom users page. my blog is @
http://dieter.plaetinck.be/
* the section "documentation" with 2 subitems, one of them being "documentation" is a bit weird.
maybe append the two links to the upmost list (i.e. add them below the link to bugtracker)
* users and registries could get their own title. like "Community". then, under
  community you could put also a link "Get in touch" which contains the mailing
  list and irc info. that might be a better place then the home page for it.
  imho the home page should be short and focused. (readable without scrolling) so if you can get the
  irc/mailing list info away from there.. maybe also remove the "Bugs/Features" section. after all there are links to that from the main menu.

Dieter