On Wed, Jul 22, 2009 at 12:51 AM, [Ricardo Rodriguez] Your EPEC Network ICT
Team <webmaster(a)environmentalchange.net> wrote:
Hi!
Pascal Voitot wrote:
Hello,
Here is my experience.
For my simple technical website (
www.mandubian.org (not ads here)), I
used a
mix between Magnolia and XWiki:
Your site looks nice!
thks ;)
- Magnolia as the content aggregator and
"visual facade" using Magnolia
easily customisable skin system, publishing/workflow features and also
for
the idea of authoring/public instances. But I
don't need anything more
from
Magnolia.
So, it seems that it is worth to invest some efforts to improve and/or
ease the skin customization application. I don't know who is actually
working in this issue, but I remember a lot of messages about the topic.
Don't you think that it is worth to invest some time/resources in
developing such an application?
yes it is worth...
I don't know who works on that now as I'm not in XWiki team but I think this
might take some time also.
Moreover, the question is: what is a good skin customization tool? (keeping
current flexible features around velocity and giving a nice wysiwyg way of
structuring your skin)...
In a summary, in magnolia, as everything is stored in JCR, everything is a
tree and then the skin is a tree. They mix this tree structure with the
templating approach. So you build your skin from the top to the bottom:
parts embedding other parts embedding other parts etc... And you can say: in
this part, I can accept only this and this and this. Then they have a kind
of MVC model to represent each part and the rendering part is managed with
the templating engine FreeMarker (velocity like).
So it is quite easy to change the skin structure.
Finally what's nice with their tool is that when you are working on your
site, you have a quick view of it and every content in it is enhanced by a
small toolbox allowing to edit, move, delete it... with that, you can
reorganize the page in a WYSIWYG way. I want this teaser to go before this
one, I want to add a new paragraph just here, to change this header or
footer here, to change the title etc... almost inline editing... not perfect
but quite practical...
Not the same approach as the wiki approach but with the xwiki wysiwyg
editor, we go in this way.
I really like the idea of changing the site from the site itself. (No I
don't want to have dreamweaver, just some features of it ;););) )
And something I like in CMS: you have an authoring instance and a public
instance of your site. You play in the authoring instance until you are
happy and then you publish from the authoring instance into the public
instance...
You guys at XWiki must be in the middle of the
now classical CMS/Wiki
conflict but I used some CMS for some time now and XWiki for some time
also
and my conclusion is that I don't see any
reason why XWiki couldn't be
used
to create nice websites.
I am not sure if this is right terms of the discussion. Is it possible
to compare a CMS with XWiki? I don't know if it is possible to compare a
CMS with other wikis, but XWiki is, if I've well understood, about using
the wiki concept to develop applications, no contents. Contents are of
course an important part of the system. Thus, publishing control and
guided edition could be killer applications.
Yes it is possible to compare and lots of people do it all the time and even
fight against each other... "I'm for CMS"... "I'm for WIKI"...
this is the
WCM, the "war for content management"... everyone wants the business of the
other one..
I prefer working on their convergence in the domains in which they can
converge...
XWiki has its own channels for proposals, so it is my responsibility to
try to write something with sense and sher it!
Mandubian is now in my bookmarks toolbar!
Keep it ;)
Don't be surprised when it seems down, this is a private server and I
perform some experience sometimes...
Greetings,
Ricardo
--
Ricardo RodrÃguez
Your EPEC Network ICT Team
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs