Hi Kito!,
Nice to see you here :)
On Jun 13, 2007, at 4:03 AM, Kito D. Mann wrote:
Hello,
Please forgive me if the answer to this question is posted
somewhere (didn’t see anything in the archives). I’d like to use
xWiki for publishing articles. I’ll be using it inside eXo portal
(I think xWiki’s lightweight approach is more suitable than eXo’s
CMS for my needs).
Have you already succeeded in running xwiki inside Exo? The
integration of XWiki as a portlet in Exo isn't perfect yet and there
are a few things to fix AFAIR regarding the albatross skin. We can
work together to make that work if you really need that integration.
The other possible integration is calling Exo services from within
XWiki. This works very well and I've demoed that already. Which means
you could do things like trigger an exo workflow, call the exo JCR
API, etc.
The only piece I’m missing is how to go about creating
a very
simple workflow. Basically, I’d like something like this:
1. Author or Editor creates an article
You can do this by creating groups and
allowing edition of docs by
Authors/Editors.
2. Author writes the article
Same as
above. If the author has the edit permission he'll be able to
write the content.
3. Editor edits the article
Here what you
could do easily is create a Status "class" within xwiki
and you'd create a template for articles and a Status object would be
attached by default to the newly created Article document.
When you create the Status class you can have a single field named
"status" which is a list of values representing the status of the
document: created, written, edited, reviewed, published.
Then it'll be up to the various individuals to edit the objects on
the article page and set the status to the valid one. Of course you
could very easily develop a little UI for it too (really simple). For
example you could write a Panel that contains a combo box with the
statuses inside and when clicked it'll change the article's Status
object accordingly.
Le me know if you need more directions for doing this. You should
read the FAQ application tutorial on
xwiki.org in the dev guide to
understand what Objects, Classes and Templates mean. Then feel free
to ask more specific questions here and I'll help you.
4. Author reviews the article
5. Steps 3 and 4 can repeat
6. Editor publishes the article
Where Author and Editor are roles that can be fulfilled by one or
more users, but Authors can only view their articles.
Above you said that authors
were writing the document but now you say
they can only view them. Do you mean that the author rights has to
vary during the workflow? If so, that's possible too but you'll need
to add velocity/groovy code to the Panel for example so that when the
status is changed the permissions are changed too for that document.
The document's permissions will override the space or wiki level
permissions for that document so that'd work nicely too.
And of course, this has to work within eXo.
This
is where there's the more work I believe. It really depends if
you're using the WebOS of Exo or the older interface. I think it
should work fine with the old interface but with webOS there might be
some tweakings of xwiki required. You may want to try it and see how
it goes.
Thanks
-Vincent