22 Jul
2009
22 Jul
'09
12:51 a.m.
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!
- 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?
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.
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!
Greetings,
Ricardo
--
Ricardo RodrÃguez
Your EPEC Network ICT Team