+1 on this change in general yes, it's a lot of pages, but one of the #1 issues people have with Jakarta is simply finding the right download.
The formatting is still iffy; I think it would be more readable in a tabular format, with a column for MD5 and a column for PGP. I would also prefer the full file name, rather than just the version number; if I click "1.0.tar.gz" I don't want to be surprised with "hivemind-1.0.tar.gz". Thanks for putting in some work on this! On Sat, 29 Jan 2005 19:17:49 -0500 (EST), Henri Yandell <[EMAIL PROTECTED]> wrote: > > Next on my list of renovations are the Jakarta download pages. Although > the cgi isn't hooked up, how do the following generated files look? > > http://www.apache.org/~bayard/jakarta/site/downloads/download.html > > In case it looks too crap (because of the missing cgi), look at: > > http://www.apache.org/~bayard/jakarta/site/binindex.html > > to see how the page normally looks when cgi is not present. > > The Commons download page is still a big list, it could also be broken > down into a separate page per component. The same could happen for > Taglibs, currently I've stayed with the link rather than having individual > Taglibs be in the download section, the aim being to change current things > as little as possible. > > There are some simple flaws that need fixing, md5/pgp's are shown even > when not available, and the mirror info, md5 info and pgp info are shown > even when they're not available. All easy to fix. Also a few missing > things like links to readme's and change-reports. Also easy enough to fix. > > Deployment-wise, my idea would be to replace binindex and srcindex with > this download.html page. It's small enough that binindex.cgi#tomcat won't > be a problem when the #tomcat fails. > > Rather than having projects linking to download.html though, they would > link directly to their particular page. So ORO would kill its current link > of binindex.cgi#oro and move to downloads/downloads_oro.html. > > The pages are created by taking a downloads.xml file, turning it into > xdocs-format pages and then turning them into html pages. The interesting > stuff is in: > > http://svn.apache.org/repos/asf/jakarta/site/xdocs/downloads/ > > I changed my original suggestion of having a dynamic page which could be > given any filename as I want to avoid having too much in the way of > dynamic stuff running. > > It's generated with 'ant -f build-downloads.xml' in the jakarta/site/ > directory, and puts the output into tmp/site/downloads/. > > Anyway. More work to do, but I wanted to see what opinions there were > before I put anymore time into cleaning it up :) > > Opinions? > > Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
