Regards,
Glen
At 11:14 AM 4/09/2003, you wrote:
The site should always show the development version. The goal of the site is to get people involved. People who want to use the releases have the release docs.
On 9/3/03 8:15 PM, "Glen Stampoultzis" <[EMAIL PROTECTED]> wrote:
>
> Yeah... it probably wouldn't hurt to show released documentation and the
> current HEAD documentation. I'll have to keep that in mind when the 2.0
> release comes around.
>
> -- Glen
>
> At 11:56 PM 3/09/2003, you wrote:
>> Something that is kind of along the same lines, especially with the upcoming
>> release, is that we need javadocs to hang off the site for the released
>> version. The javadocs for the development version can still be on the page
>> but possibly in a sub menu (tab?) on development. This would avoid some
>> confusion with uses who see a certain feature available in the javadocs but
>> does not work because they have the most current release and not the head.
>>
>> I do realize that this is still in on going development but we are starting
>> to getting a good enough release and large enough base that many want
>> need/want to use the development head.
>>
>> Shawn
>>
>> -----Original Message-----
>> From: Glen Stampoultzis [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, September 03, 2003 6:08 AM
>> To: [EMAIL PROTECTED]
>> Subject: POI Website
>>
>>
>>
>> As the project as matured the POI web site has grown organically to
>> accommodate that growth. Unfortunately I think we're now at the stage were
>> things are a bit messy and it's not holding together as well as it once may
>> have.
>>
>> I'd like to open up discussions as to what you think the main problems are
>> and some idea's how we might fix them without having to invest huge amounts
>> of time in complete rewrites.
>>
>> I'll kick it off with a few things I can see:
>>
>> Problem) Some of the content is out of date.
>> Potential Solution) Identify out of date content and rewrite it.
>>
>> Problem) The navigation system is kind of awkward.
>> Potential Solution) Tabs for each project?
>> Potential Solution) More clearly defining user oriented content and
>> developer oriented content.
>> Potential Solution) Maybe using forrest sitemaps will give us better
>> control.
>>
>> Problem) How do we keep the translations up to date? For instance I just
>> noticed that the german translations still point to the old download
>> location.
>> Potential Solution) Need owner for each translation who is willing to
>> watch for changes as they come through.
>>
>>
>> Regards,
>>
>>
>> Glen Stampoultzis
>> [EMAIL PROTECTED]
>> http://members.iinet.net.au/~gstamp/glen/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> Glen Stampoultzis
> [EMAIL PROTECTED]
> http://members.iinet.net.au/~gstamp/glen/
>
-- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi For Java and Excel, Got POI?
The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Glen Stampoultzis [EMAIL PROTECTED] http://members.iinet.net.au/~gstamp/glen/
