Re: Fwd: Project Status

On Jan 20, 2008, at 1:13 PM, Tim Diggins wrote:
> 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.

I've simply never revisted the tutorial to make it part of the  
generated pages. For that reason, anything under the doc directory is  
included in the site as is. Yes, it would be good to recode the  
tutorial. One sub-project I've never completed was going to let the  
build actually test the code in the tutorial to make sure it worked.  
That would have involved generation of those pages from templates.

>
> 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?

In general, I like having the side menu, both due to its appearance  
and ability degrade on browsers that do not support CSS (although that  
is admittedly much less common, nowadays). I would have to see how  
your modified menu idea looks to comment.

Do you want to submit a patch to make some of those changes?

-------------------------------------------------------------------------
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