Re: Fwd: Project Status
Tim Diggins <[email protected]>
| Newsgroups | gmane.comp.web.httpunit.devel |
|---|---|
| Message-ID | <[email protected]> |
On 19 Jan 2008, at 23:32, Russell Gold wrote: > On Jan 19, 2008, at 4:50 PM, Tim Diggins wrote: >> 1) website mods: >> ------ >> In terms of the website, should I go ahead and try to make some >> suggested amendments to the website and then mail them back? > > Absolutely. >> >> However, the site seems to be composed from 'quicksite' base jar plus >> the site package with some xml & html files in sitedocs. It looks >> like >> the site is determined by the site.xml file, but is there any easy >> way >> of previewing/generating html (with quicksite + site package I >> assume). > > I think the generation is fairly simple and controlled by the > build.xml. I generate locally to see what it looks like first. Yes - didn't realize (duh - why not?) that it was built by ant - (by the 'publish' task). However, I'm confused as to why there's a separation between doc and sitedoc -.e.g there's a file sitedoc/tutorial.html file which is an introduction to doc/tutorial/* - there's also a folder sitedoc/doc. A drawback of the current arrangement is that when you go from tutorial.html to the first page of it, you lose the overall left-hand menu navigation & site template. It strikes me that it would be easier if there was only one hierarchy - one of the things I found confusing before with http-unit is that the docs you find in the website isn't the same as what you get when you download the distro. Is there a reason for this, or could it be changed and all integrated? I haven't totally got my head around the site generation mechanism so can't guess how much effort this is... Overall, I'd like to see the navigation much simpler: the main sections/pages people want are - Home (with overview, news and link to developers) License Downloads (a page which could be a download link to the current version (1.6.2) and a a link to the sourceforge downloads page) and a link to subversion repository) Documentation (some kind of overview of the different documentation available - tutorial, cookbook, javadocs, javascript support, servletunit intro and faq) Support and links (a page with links to faq, mailing list page, bug + feature process (with link to bug repos) AND a request to donate to HttpUnit Press ( == External Citations) This menu could then be much smaller and then fit in a vertical format across the page. There could then be secondary menu with direct links to the bug/feature process and a donate to http unit (and any other links that are deemed useful). This is a fairly common structure (good - unremarkable == This would also make it easier to integrate new content into the site / docs. This would mean writing a documentation overview page to pull these resources together - the other pages are quite minor and easy to write. What do you think? Tim ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Httpunit-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/httpunit-develop