Jonathan Locke wrote:
i'd like to shorten and simplify the wicket vision doc to just a coupleI'd rather make the discussion a bit larger to encompass the whole contents of our website. I hope the stuff I write here makes some sense (it was late last night, and the job is killing me somewhat).
paragraphs on a single page and possibly move the q&a parts of it to
another page. do people like this idea? if so, i'm happy to do that. someone may need to kick me though as i'm pretty scattered right now...
Currently the website has the following menu:
_Wicket_
Home -> the main entry page containing sales pitch for Wicket, latest news and supporting partners (sourceforge, clover, etc)
News -> news archive for announcements etc.
Introduction -> Your original Introduction document
_Getting started_
Download -> a link to the download section (perhaps better to link it to the quickstart project download)
Quick start -> now too small, too little info (documentation for the quickstart project?)
Examples -> current 5 examples
_Project info_ Mailing Lists -> overview of the mailinglist generated by maven SourceForge -> overview of the sourceforge.net pages Changes -> overview of the closed issues grouped by release
_Documentation_
User's manual -> link to the PDF version of Jonathan's original manual
Wiki -> link to the wiki part of our website
Examples -> same page as with the _getting started_
Javadoc -> Link to the API documentation
The Wicket Vision -> link to the Vision document
Dependencies -> the required jars page, generated in the maven.xml file (as opposed to the included report of maven).
_Wicket development_
Developers -> maven generated list of contributers
CVS access -> maven generated page of CVS access to the Wicket sourcecode
Build reports -> maven generated reports (javadoc, unittests, clover, etc.)
I would like to keep this structure, but change the contents of each page, or (re)move some pages.
The way I see the website is as follows. People visiting the website have different goals:
- what is Wicket
- can I use Wicket
- how do I use Wicket
- getting support
- contributing to Wicket
And these people have different backgrounds:
- 'newby' webdevelopers, having read some reviews about wicket
- seasoned webdevelopers, wanting to try something new
- architects, trying to make a decision to use JSF, tapestry or something else
- opensource addicts, trying to find a project to contribute to
Each of these people find different information valuable:
- the License (i.e. can I use the software)
- the documentation (is the documentation any good, or do I need the sourcecode?)
- is the project actively maintained (how many developers/admins are there, is the mailing list active)
- etc.
The following structure seems more natural to me. I want the site to be more of a leaflet, flyer, etc. as a 'commercial' exposition of Wicket and a place for documentation, rather than an operational site. For most projects I don't look at the results of the unittests, clover reports etc. These can be placed in the daily builds section.
I also want to give some space to the other spinof projects, like contributed components. Are there other projects we need to give some space in the menu?
Wiki content:
We have previously discussed putting links to projects using wicket on the site. I think those could perfectly go into the Wiki. Also, faqs, configuring tomcat, jboss, websphere, etc. should go into the wiki.
_Wicket_ -> goal : introduce Wicket Home Introduction License -> Apache license
_Getting started_ -> goal : Download wicket distribution quickstart Quick start Examples
_Documentation_
User's manual -> (new) contents as 1 page html, multipage html in the wicket style, pdf
Reference -> component reference?
Wiki
Examples -> changed contents with more elaboration (copy/paste from manual?)
HelloWorld
...
Displaytags -> Nice examples Juergen!!!! need to show some of them in the examples section.
Javadoc
_Project info_ News -> news archive Dependencies Mailinglists Sourceforge Issue tracker -> direct link to the sourceforge page.
_Wicket development_
Developers
CVS Access
Code conventions -> new document(s) stating the placement of curly braces, package names, and the need to 'discuss first, do later'
Building Wicket -> new document explaining the process to perform a build (and a release?)
Daily builds -> generated site(s) by cruisecontrol or the sourceforge compile farm, showing the unittest results, clover reports, etc.
Martijn
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Wicket-develop mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
