I agree, that a large banner pointing to documents for current Wicket
version would be a good idea.
I also arrived at these old pages via Google, and it took me a while
to understand that its' about older versions.

regards,
Maarten

On Tue, Jun 3, 2008 at 8:44 AM, Antony Stubbs <[EMAIL PROTECTED]> wrote:
>
> In that case I would suggest a large banner at the top of every page
> proclaiming that fact, and a large link to the new site.
>
>
> Martijn Dashorst wrote:
>>
>> This has been discussed OVER and OVER. the 1.2, 1.1 and 1.0 websites
>> are for archive purposes, and still available for Google to index!
>> This is on purpose, exactly for those that come across an older Wicket
>> based application.
>>
>> Martijn
>>
>> On Tue, Jun 3, 2008 at 8:02 AM, Antony Stubbs <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Woah - that's old.
>>>
>>> http://wicket.sourceforge.net/faqs.html
>>>
>>> I know http://wicket.sourceforge.net/ redirects, but google still index's
>>> it's sub content, and so points people there when looking up wicket
>>> issues.
>>>
>>> Something needs to be done about that - perhaps redirect all requests to
>>> that domain? Or simply remove the html content.
>>>
>>> Would you like me to create a Jira for it?
>>>
>>> -----
>>> ___________________________
>>>
>>> http://stubbisms.wordpress.com http://stubbisms.wordpress.com
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Sourceforge-page-needs-to-come-down-tp17616570p17616570.html
>>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.3.3 is released
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
>>
>>
>
>
> -----
> ___________________________
>
> http://stubbisms.wordpress.com http://stubbisms.wordpress.com
> --
> View this message in context: 
> http://www.nabble.com/Sourceforge-page-needs-to-come-down-tp17616570p17617018.html
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>

Reply via email to