Jonathan Locke wrote:
here's the stuff i see right now... i'm being pretty picky, but i just tend to be the "type A" personality that sees this sort of stuff really easily...
Being picky is no problem, not being able to withstand 'no' is :-)
I think you've missed my comments on your message concerning the vision document (http://www.mail-archive.com/wicket-develop%40lists.sourceforge.net/msg00552.html). In this message I layout my vision for the wicket website. Most of my comments and negative votes find their source in that vision.
- would prefer that introduction and vision sections not have sublinks in the side nav. they're not that big.
+0, they do give some hints on what's in the document. I'd rather have a rewrite altogether. I think the introduction could use more vision, and the vision could be smaller, or even absent as a seperate document. I think it could be in the reference manual, or the user's guide.
- would remove examples from documentation section since it's under getting started
-1. I think the examples need some rewriting, and that they are perfectly placed: getting started has direct access to get people up to speed. The documentation section provides background. The examples are both: showing directly how stuff is done, and a reminder of how things are done.
The examples document needs to be updated to the newest API changes, and each example could get its own page, possibly even a link to an online server displaying the example.
- would move vision link up under wicket link group just below license link
See my previous remark. I think the vision document should be at best documentation, but I could also live with it residing in the wiki.
- would change "Wicket Development" group name to just "Development" (we already know it's wicket)
I wanted to diffentiate between 'Development' as development of webapplications using wicket, and developing wicket as a framework. The links provided are also different.
- on the home page "/Find out/ Why you should use wicket" should lowercase the "Why" and uppercase the "Wicket"
ok. (was copied from the original website :-)
- would prefer some new link color (faded orange, sky blue?) throughout. you cannot tell that "why you should use wicket" is a even a link in my firefox browser since the color matches the text exactly and there is no underline. this buries the link and makes the sentence kindof odd.
My firefox shows a line under the link, so does my 'virgin' IE 6. The designer explicitly allowed underlines for links. Perhaps something wrong with your firefox, platform wise?
- would change "Welcome to Wicket" to just "Welcome!"
-1, as my eyes are immediately drawn to the orange text in the middle of the screen, and the logo in the upper-left corner doesn't make too much an impact on me. This way I immediately know it's the wicket website.
- would consider moving all the stuff under "Project info" into the top "Wicket" section. in other words, we'd just have "Wicket / Getting started / Documentation / Development"
-1. The goals of the sections are different: first one needs to find what this wicket thing is, and the first time user finds this on the top of the website. Then one needs to figure out how to get started. Then one needs more information on how to proceed (documentation). When that doesn't help, more information is needed on getting help (issue trackers, mailinglists, etc). Last in the line are the developers of wicket itself. Actually, the current order is off a bit: documentation and project info should switch.
- under Latest News "now in the top level package name |wicket|." should read "now in the top level package named |wicket|."
OK.
- some text was cut out of the introduction just after the list of frameworks, making the next paragraph reference something that was never stated
Do you remember that text?
- in the introduction "Swing-like omponent model" should be "Swing-like component model"
OK.
Thanks for your attention to detail :-) I hope to get some discussion going on concerning the documentation/website just like we discuss java code. A project can fail for lack of attention to the documentation. We have a decent site, now let's make it just as good as Wicket is.
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
