Mailing-List: contact cayenne-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cayenne-user@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <ee04ee7f0609090746r3ad027c5hd62cebc90870bb04@mail.gmail.com>
References: <ee04ee7f0609081127h5af113b2uf453a16290df18fc@mail.gmail.com>
 <C9DDDF6D-5AA0-42F0-8E62-B21B2B1DAB15@ish.com.au>
 <2A11D5D7-4F22-4B54-8C88-32A667F3FDE9@objectstyle.org>
 <ee04ee7f0609090610n170d470djc80fc24929664912@mail.gmail.com>
 <ABAF5008-0A8B-411E-8C15-393BF7DF63EA@objectstyle.org>
 <ee04ee7f0609090746r3ad027c5hd62cebc90870bb04@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <D68A6EF7-9481-47C7-8A1E-AE09C590BCFE@objectstyle.org>
Content-Transfer-Encoding: quoted-printable
From: Andrus Adamchik <andrus@objectstyle.org>
Subject: Re: Site structure redesign
Date: Sat, 9 Sep 2006 19:27:19 +0400
To: cayenne-user@incubator.apache.org


On Sep 9, 2006, at 6:46 PM, Borut Bol=C4=8Dina wrote:

> I can live with that, it's just that it discards my idea of two site
> focuses. We can experiment, I think we are all very open minded ;-)

This is where I misunderstood your intent initially. I think I follow =20=

you now. See my other message on site focus - we need to accommodate =20
all those users. How we split it across the site(s) is the question =20
to discuss, but there is no question that all those aspects need to =20
be addressed in some way.

> Don't you think we can profile the users based on user mailing list =20=

> postings
> and decide which items are more important?

I used to run webalizer stats from the old objectstyle site. IIRC =20
JavaDocs generated lots of hits; same for the user guide. This points =20=

to the people who are actually working with Cayenne and are looking =20
for the reference material. Not sure how useful FAQ is in its present =20=

state.

> No one wants to write documentation in XML, at least sane people =20
> don't. If
> this auto export can make the static site visually professional =20
> then maybe
> the static site can only have titles and excerpts with link to wiki =20=

> entries.

Yep. Content transformation (from Wiki to static) is done using this =20
Velocity template that I mentioned before:

http://people.apache.org/~aadamchik/confluence-template.txt

Right now it generates Confluence standard look, we can change it to =20
anything we want. If the template above turns out to be not flexible =20
enough, all Confluence content is accessible via XML-RPC and SOAP =20
(both are very easy to use), so we can get the raw content and format =20=

it to our liking. That's how we produce downloadable user guide.

> Yes, it looks quite ok. Then again  have a look (click through some
> sections) how differently it can be done
> http://www.oracle.com/technology/products/ias/toplink/quicktour/=20
> index.htm.

Not very impressed by this powerpointish site, but I agree that we =20
need some sort of feature walk-through section. Don't see any =20
conflict with having that type of info and the current site.

Andrus