De : BARDE, CEDRIC [mailto:[EMAIL PROTECTED]]
>
> Hi Rapha�l,
> Thank you veyr much for your advice. I think the solution you
> talk about can
> meet my needs. We are currently in the very first step of
> setting up our
> portal, so the editorial workflow process is not very
> complicated. What
> content production tool would you advise me to use, in order
> to be easy to
> integrate with Jetspeed?
Any RSS producing tool really, but you can usually add RSS export
capabilities to any web-based content system.
My original setup used a legacy custom publication system, nowadays
I'd probably use a Wiki depending on the kind of content
you want to publish and how your users are expected to used to do
things.
Ultimately it boils down to how you see your system evolve. This
is question which I don't have enough data to answer :)
Your choice will also be conditioned by the kind of technology
you're willing to support (ie java, perl, php, python, etc...).
Just 2 examples out of my head:
- setup a Jabber IM system + Jogger weblog interface + RSS export
-> ultra-easy content generation for informal and unstructured
content (suitable for example for event announcement and
breaking news)
-> setup a Wiki tool (too many exist to really to list, google for wiki
software). Most have RSS export capabilities.
-> collaborative editing of documents with simple style capabilities
(BTW, I'm currently updating the Jetspeed RSS stylesheets to
support the Apache Wiki generated content
http://nagoya.apache.org/wiki/apachewiki.cgi)
Of course you can setup as many as these tools as required... they will
all be syndicated in the same way.
--
Rapha�l Luta - [EMAIL PROTECTED]
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
