On Thu, 23 Aug 2012, Robert Muir wrote:
On Thu, Aug 23, 2012 at 12:51 PM, Andi Vajda <va...@apache.org> wrote:
I can now retract my 'crying shame' comment on the site. A bunch of work is
still needed but there is enough critical mass there to get the formatting
correct proceeding by example. Before it was a "oh, where do I even start,
kind of mess"
A few things i noticed (in general I didnt want to try to change
content or anything like that but just fix formatting and links so
things are readable and work)
* does pylucene have a logo?
it currently uses the lucene logo. on the other hand, if we want to
keep the current logo we could at least apply the shadow'd apache
feather to make it nicer: compare the lucene logo at
http://lucene.apache.org/ with http://lucene.apache.org/pylucene
No, it doesn't have a logo. I think using Lucene's logo is fine.
If people disagree and want to contribute a logo, by all means !
* does pylucene want the slides functionality that is on
http://lucene.apache.org/core/ and http://lucene.apache.org/solr ? if
so we just need a list of some 'text snippets/slogans' to rotate
through, could probably reuse the lucene core images.
I don't think it's a must but if people want to contribute text snippets and
set that up, it sure looks nice.
* should the pylucene download button appear under jcc/ pages? I
wasn't sure if it should, but thats easy to fix.
Yes, but it should then point at the http://pypi.python.org/pypi/JCC/2.13
URL which might be a bit touchy with regards to Apache's rules.
* pylucene and jcc "Features" pages are really "Documentation", this
is a little confusing. I think the link should be renamed
"Documentation" and maybe have a separate features list like
http://lucene.apache.org/core/features.html ?
Agreed. Their current name came over from the 'forrest' content.
* the application of italics/bold is somewhat arbitrary: I did this
because previously these had <code>...</code> which causes a big blue
blockquoted section with line breaks, useful really for code examples
but not for reference to functions or class names. If there is some
defined scheme (java class name monospace, functions italics, command
lines and arguments bold, or whatever), it could probably be more
consistent.
Looks great to me. I originally wanted all code to use a fixed width font
and respect the indentation of the source file, thus the code blocks. This
worked fine with Forrest but markdown thinks differently. As long as what
replaces the fixed width font for code is used consistently and respects
indentation so that code sames are legible, I'm happy with the change.
* maybe in addition to the download 'button' there should also be a
simple page with the information about how to retrieve older versions
from the apache archives etc. (similar to
http://lucene.apache.org/core/downloads.html)
+1 !
Andi..
