For the actual docs, Confluence has a WYSIWYG editor so people don't even
have to learn wiki markup for most of it. You can even cut and paste from
most windows apps (e.g. office etc.) into it and it preserves formatting
etc.
Admittedly you need to know velocity to do more advanced stuff like custom
themes etc.
On the MINA list, the consensus opinion appears to be that the Maven site
is a bit of a barrier to contributing docs and that a wiki would be better
(not dissimilar to what you describe from CeltiXfire).
RG
|---------+---------------------------->
| | "Johnson, Eric" |
| | <[EMAIL PROTECTED]|
| | a.com> |
| | |
| | 20/09/2006 16:58 |
| | Please respond to|
| | qpid-dev |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: <[email protected]>
|
| cc:
|
| Subject: RE: Qpid project Web Site
|
>------------------------------------------------------------------------------------------------------------------------------|
The exact opposite argument was put forth in the CeltiXfire discussion.
I was pushing for using HTML or some form of XML and the developers said
they felt more comfortable using a wiki to contribute documentation.
I took a look at the Tuscany and Maven sites that Carl likes and it
looks like they are built using the Maven site plug-in. Tuscany does a
better job with the skinning from my perspective. I just used HTML to
get the simple CeltiXfire(http://incubator.apache.org/cxf/) stuff up I
just used plain old HTML. It was the fastest approach at my disposal.
I can send out a zip with some basic stuff this afternoon and we can see
if we like the basic structure. Then we can decide the best way to build
the stuff going forward.
> -----Original Message-----
> From: Rajith Attapattu [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 20, 2006 10:42 AM
> To: [email protected]
> Subject: Re: Qpid project Web Site
>
> Eric,
>
> I have no particular preference, but my worry about cwiki is that
people
> might have to learn it before they contribute with documentation.
> As with the maven site building stuff people can write simple html
which
> gets converted to xdocs using some maven pluggin which seems more
easy.
>
> Either way I can help you out on the efforts. Lets agree on a site
layout
> and we can start sharing the workload.
> We might also have to start getting the others involved for atleast a
> basic
> user guide and architecture guide.
>
> Regards,
>
> Rajith
>
> On 9/20/06, Johnson, Eric <[EMAIL PROTECTED]> wrote:
> >
> > The CeltiXfire project is also looking at using cwiki for its main
site
> > and its documentation. I'm still not convinced about it being a
great
> > idea, but the Wiki does make editing easy. There is no messing
around
> > with HTML or XML files.
> > It is a regular Confluence wiki and does have the ability to do
static
> > export of the content. To get the stuff to look really good though
you
> > need to create export themes using Confluence's theme engine which
uses
> > Velocity. Without the theme it looks pretty terrible.
> > What Geronimo did, and CeltiXfire is going to emulate, is create
several
> > spaces on cwiki for the project. One space is the where the main
site is
> > created and has pretty restricted access. The other spaces have
> > different access privileges and are used for documentation and
developer
> > spaces. This provides some flexibility around access control and
look
> > and feel.
> > I've done a little poking around with the theme stuff and it does
not
> > look too hard. I haven't actually gotten around to creating and
testing
> > one though.
> > Another option is to use the Maven site building stuff. It is also
> > pretty powerful and can be skinned.
> >
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, September 20, 2006 3:41 AM
> > > To: [email protected]
> > > Subject: Re: Qpid project Web Site
> > >
> > > On the MINA list, the project lead is asking for opinions on
moving
> > all
> > > their stuff to cwiki, which seems to be a Confluence-based hosting
(I
> > am
> > > not exactly sure how it differs from plain Confluence?). He
indicated
> > it
> > > had a static site capability.
> > >
> > > He linked to this example site, which is used by Geronimo:
> > >
> > > http://cwiki.apache.org/GMOxSITE/index.html
> > >
> > > RG
> > >
> > >
> > > |---------+---------------------------->
> > > | | Carl Trieloff |
> > > | | <[EMAIL PROTECTED]|
> > > | | t.com> |
> > > | | |
> > > | | 20/09/2006 01:22 |
> > > | | Please respond to|
> > > | | qpid-dev |
> > > |---------+---------------------------->
> > >
> >
>-----------------------------------------------------------------------
> > > -------------------------------------------------------|
> > > |
> > > |
> > > | To: [email protected]
> > > |
> > > | cc:
> > > |
> > > | Subject: Re: Qpid project Web Site
> > > |
> > >
> >
>-----------------------------------------------------------------------
> > > -------------------------------------------------------|
> > >
> > >
> > >
> > >
> > >
> > > Eric,
> > >
> > > It would be great if you take the first pass. I do however prefer
the
> > > layout of
> > > Maven and Tuscany for example over most of the others. It would be
> > great
> > > if
> > > you could model it more of one of those two.
> > >
> > > Carl.
> > >
> > > Johnson, Eric wrote:
> > > > Does anyone have interest in picking this up? If not I'll make a
> > first
> > > > pass at it. I did the first pass at the CeltiXfire site. It is
> > pretty
> > > > basic, but it is a start.
> > > >
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Rajith Attapattu [mailto:[EMAIL PROTECTED]
> > > >> Sent: Sunday, September 17, 2006 12:36 PM
> > > >> To: [email protected]
> > > >> Subject: Re: Qpid project Web Site
> > > >>
> > > >> Hi All,
> > > >>
> > > >> Before we do a release it's good if we can get our web site up
and
> > > >> running.
> > > >> The website will provide us with a platform to get our
> > documentation
> > > >>
> > > > up
> > > >
> > > >> and
> > > >> running as well.
> > > >>
> > > >> The following link describes the layout and the procedure.
> > > >>
> > > >> <http://incubator.apache.org/incubation/Incubation_Policy.html>
> > > >> http://incubator.apache.org/guides/sites.html
> > > >>
> > > >> comments/suggestions/ideas most welcomed.
> > > >>
> > > >> Regards,
> > > >>
> > > >> Rajith
> > > >>
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > > This communication is for informational purposes only. It is not
> > intended
> > > as an offer or solicitation for the purchase or sale of any
financial
> > > instrument or as an official confirmation of any transaction. All
> > market
> > > prices, data and other information are not warranted as to
> > completeness or
> > > accuracy and are subject to change without notice. Any comments or
> > > statements made herein do not necessarily reflect those of
JPMorgan
> > Chase
> > > & Co., its subsidiaries and affiliates.
> > >
> > > This transmission may contain information that is privileged,
> > > confidential, legally privileged, and/or exempt from disclosure
under
> > > applicable law. If you are not the intended recipient, you are
hereby
> > > notified that any disclosure, copying, distribution, or use of the
> > > information contained herein (including any reliance thereon) is
> > STRICTLY
> > > PROHIBITED. Although this transmission and any attachments are
> > believed to
> > > be free of any virus or other defect that might affect any
computer
> > system
> > > into which it is received and opened, it is the responsibility of
the
> > > recipient to ensure that it is virus free and no responsibility is
> > > accepted by JPMorgan Chase & Co., its subsidiaries and affiliates,
as
> > > applicable, for any loss or damage arising in any way from its
use. If
> > you
> > > received this transmission in error, please immediately contact
the
> > sender
> > > and destroy the material in its entirety, whether in electronic or
> > hard
> > > copy format. Thank you.
> > >
> >
> >
This communication is for informational purposes only. It is not intended as an
offer or solicitation for the purchase or sale of any financial instrument or
as an official confirmation of any transaction. All market prices, data and
other information are not warranted as to completeness or accuracy and are
subject to change without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and
affiliates.
This transmission may contain information that is privileged, confidential,
legally privileged, and/or exempt from disclosure under applicable law. If you
are not the intended recipient, you are hereby notified that any disclosure,
copying, distribution, or use of the information contained herein (including
any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other defect that might
affect any computer system into which it is received and opened, it is the
responsibility of the recipient to ensure that it is virus free and no
responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
affiliates, as applicable, for any loss or damage arising in any way from its
use. If you received this transmission in error, please immediately contact the
sender and destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
