Hello, Here is my experience. For my simple technical website (www.mandubian.org (not ads here)), I used a mix between Magnolia and XWiki: - 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. - XWiki as the content provider with a small plugin I developed in order to integrate XWiki into Magnolia. XWiki provides a much simpler and concrete way to create my content because my website is not a commercial site or sport news site.
In a summary, I write with XWiki and I publish with Magnolia. So everything is not perfect and well integrated but it works and I can publish my small articles quite easily. In fact, beyond some publishing and workflow features that XWiki lacks, the reason why I chose to use Magnolia CMS for the "what you see" and XWiki for the "what you get" is the skin issue: I can't spend too much time customizing the skin and I need a "practical" base for this: - a nice skin with all the stuff a website usually provides (menus, teasers, panels, events, columns, etc...) - A wysiwyg way to modify the skin and re-organize the structure of the presentation Magnolia (and other CMS) provides it. XWiki provides everything to do it but not "out of the box" and you need to customize everything manually. I customized XWiki skin for some sites focused on the "Wiki" features but for a public website, this consumes too much time. 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. regards Pascal On Sat, Jul 18, 2009 at 11:35 AM, Ludovic Dubost <ludo...@xwiki.org> wrote: > > Hi, > > Indeed, XWiki is very close to a CMS and actually often used for this > (we use it for xwiki.com and xwiki.org). > > When you look at it, most CMS work like this: > > 1/ Admin interface allowing to create a page, setup where it will show > up (on the home page, in a category menu, in a tag menu, in a Tree menu) > but not yet publish it > 2/ Review with simple (most often) or more complex workflow > 3/ Decide to publish it > 4/ Once it's publish it shows up > 5/ Then you have tool too manage the result (delete, view stats, etc..) > > The main difference with XWiki is the way you make the page show up on > the end site. > In a Wiki you are told to first create the link, then edit the page, > which makes the page show up right away. This makes the review part not > work at all. > Another difference is that you might want to be able to make a bit more > complex pages in a CMS (columns and so) > > However the Blog is not that different from the CMS part, if we added > the review and more control of where the page shows up. > In a Blog you are very temporal. In a CMS you might not want the page to > show up in the Home page at all. You just want the page to show up where > you said it should show up. > > I'm not sure if what you suggest is what you are saying. I think you are > more talking about the complex page issue. > On this matter we discussed this on a projet last friday where we need > columns in the page and we thought the Wysiwyg could handle columns. > > It would be good to review what CMS do and integrate this nicely in > XWiki, as people more and more want to mix Publishing Web site with > collaborative ones. > > Ludovic > > Andreas Schaefer a écrit : > > Hi > > > > Currently our company is using Magnolia (magnolia.info) as the CMS for > our website. Because our website is not very dynamic, big or complex using > Magnolia is often a little bit of an overkill and keeping it up to date is > not easy. So I was wondering if I could use XWiki to create a simple > application that would enable the creation and maintenance of a website. > > > > Today the Blog is a list of Blog Document building up the blog page. > Breaking up the page into a header, left and right side bar (or using the > panels) and columns for the content it should be possible to define a web > page. The parts of a page a defined by classes and the content is provided > by objects. The application just provides the code that displays the web > site and additional elements to create, edit and remove parts of the > document (paragraphs) when the user is in edit mode. > > > > The application would provide a simple web site but also the framework to > create a custom web site by extending the application. > > > > What do you think? > > > > Andreas Schaefer > > CEO of Madplanet.com Inc. > > EMail: andreas.schae...@madplanet.com > > schaef...@me.com > > Twitter: andy_mpc > > AIM: schaef...@me.com > > _______________________________________________ > > devs mailing list > > devs@xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > > -- > Ludovic Dubost > Blog: http://blog.ludovic.org/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > > _______________________________________________ > devs mailing list > devs@xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
