On Mon, Aug 18, 2008 at 1:00 PM, Allan Ditzel <[EMAIL PROTECTED]>wrote:

> Right now the export plug-in is taking the cwiki content and exporting it
> to
> html with the standard confluence LnF. There's a template file that Alan
> sent me that I need to modify in order to change the LnF.


Where is this being generated to?  Can we see it? (I'm just curious on how
the process works exactly - how often does it occur, where are the generated
files, etc)


> The one nice feature of confluence is that you can easily search for
> content
> on the site. Granted, a well-laid out web site that is easily navigable
> making content easily available does a great deal to lessen the need to
> have
> search (i.e. if you can find the content easily from the menu, there's not
> too much of a need to search for it).


Check out the CouchDB approach for search:  Visit
http://incubator.apache.org/couchdb/

and then the very first link at the top of the nav bar on the left is the
Search link.  Click it and it takes you to a "Gooble Custom Search" page:

http://www.google.com/coop/cse?cx=006426053638666134111:bfy4xffxeqc

Which apparently aggregates the sources you select (regular site, mailing
list archives, etc, etc).

I'm assuming that we could use this to mitigate any potential loss of good
search if we didn't use cwiki.  In fact, even if cwiki was perfect for our
website needs,  we might still want to do the google custom search page
because cwiki doesn't handle the mailing list archives.  Sounds like a cool
idea to me.


>
> To be honest, I find the cwiki export mechanism to be rather cumbersome.
> Having to go through a third party to install a new template file to change
> the LnF is less than ideal. So, having said that I would prefer to work
> with
> a manually maintained site, unless using something like drupal is still an
> option. Like Les, having to use cwiki really rubs me the wrong way.
>
> Allan
>
> On Mon, Aug 18, 2008 at 12:45 PM, Les Hazlewood <[EMAIL PROTECTED]
> >wrote:
>
> > So I know we've been talking about using the apache cwiki (Confluence) to
> > generate our normal website.  Allan, where do we stand on this?  Will it
> be
> > sufficient for our needs?
> >
> > I started thinking about this, and I'm a _real_ stickler for a really
> nice
> > looking website.  I want to to be clean, look good and be easy to
> navigate.
> > I'm not a fan of Maven generated web sites, nor do I like the default LnF
> > of
> > Confluence.
> >
> > I do however like JSecurity's current website (it definitely could look a
> > bit nicer though).  I'm also impressed with Wicket's website (cwiki
> > generated), as well as CouchDB's (
> > http://incubator.apache.org/couchdb/index.html), which looks manually
> > written.
> >
> > In the last few years, I've been incredibly happy with Drupal for
> managing
> > our website.  When we move to ASF permanently, it appears that we won't
> > have
> > that at our disposal.  So, my question is, are you guys OK with using
> > cwiki?  Or would you be ok with a manually maintained and published
> > website?
> >
> > I think my current preference is the manually maintained one.  I rarely
> > update the JSecurity website today, and do so only for the occasional
> > announcement and product release - something that would still be easy to
> do
> > in a manually maintained site environment (e.g. checked in to SVN).  For
> > some reason, I just don't feel CWIKI is flexible or configuable enough
> for
> > our needs, and the "no linking to the wiki" rule really rubs me the wrong
> > way.  I don't like that anyone visiting our website would have to know to
> > adhere to weird linking rules - its just not in the spirit of the web and
> > could be confusing for some people.
> >
> > We could always link to the wiki for end-user-editable content, but maybe
> > the main website is developer-maintained only.  What do you guys think?
> > Allan, what is your opinion of Confluence and do you think it is good for
> > us
> > moving forward?
> >
> > Thanks for any feedback from anyone,
> >
> > Le
> >
>

Reply via email to