francois.ledroff@atosorigin.com Francois Le Droff en xwiki 0.9.840 32 GNU LGPL http://www.xwiki.org http://www.xwiki.org 1.7 wiki xwiki

Generic criteria from QSOS version 1.6 Intrinsic durability Maturity less than 3 months if between 3 months and 3 years after 3 years 2 Unstable software with numerous releases or patches generating side effects Stabilized production release existing but old. Difficulties to stabilize developpement releases Stabilized software. Releases provide bug fixes corrections but mainly new functionalities 1 Software knows several problems which can be prohibitive No know major problem or crisis History of good management of crisis situations 1 Software is very likely to be forked in the future Software comes from a fork but has very few chances of being forked in the future Software has very little chance of being forked. It does not come from a fork either 2 Adoption by community and industry Very few users identified Detectable use on Internet Numerous users, numerous references 2 None Few refences, non critical usages Often implemented for critical applications 2 No community or without real activity (forum, mailing list, ...) Existing community with a notable activity Strong community: big activity on forums, numerous contributors and advocates 2 No book about the software Less than 5 books about the software are available More than 5 books about software are available, in several languages 0 Organisation and leadership of developments 1 to 2 individuals involved, not clearly identified Between 2 and 5 independent people More than 5 people 2 5 admins Complete dictatorship Enlightened despotism Council of architects with identified leader (e.g: KDE) 1 Out of 5 Admins, Ludovic Dubost, Jeremi Joslin and Vincent Massol are the main drivers. Activity of the project and around the software Less than 3 developers, not clearly identified Between 4 and 7 developers, or more unidentified developers with important turnover More than 7 developers, very stable team 2 56 developpers Slow reactivity in forum or on mailing list, or nothing regarding bug fixes in releases note Detectable activity but without process clearly exposed, loing reaction/resolution time Strong reactivity based on roles and tasks assignment 2 the process is clearly exposed (mainly through jira), the resolution are not always fast No or few new functionalities Evolution of the product driven by the core team or by user's request without any clearly explained process Tool(s) to manage feature requests, strong interaction with roadmap 1 Very weak activity on both production and development releases Activity on production and developmenet releases. Frequent minor releases (bug fixes) Important activity with frequent minor releases (bugs fixes) and planned major releases relating to the roadmap forcast 2 Industrialization level of the project Developments realized at 100% by employees of a single company 60% maximum 20% maximum 1 The core developpers are in Ludovic Dubost team, He is the founder of Xpernet, the xwiki editor. Services offering No offer of training identified Offer exists but is restricted geographically and to one language or is provided by a single contractor Rich offers provided by several contractors, in serveral languages and split into modules of gradual levels 1 http://www.xwiki.com/xwiki/bin/view/Company/Training+Services No offer of support except via public forums and mailing lists Offer exists but is provided by a single contractor without strong commitment quality of services Multiple service providers with strong commitment (e.g: guaranteed resolution time) 1 http://www.xwiki.com/xwiki/bin/view/Company/Support+Contracts No offer of consulting service Offer exists but is restricted geographically and to one language or is provided by a single contractor Consulting services provided by different contractors in serveral languages 1 http://www.xwiki.com/xwiki/bin/view/Company/Development+and+Consulting No user documentation Documentation exists but shifted in time, is restricted to one language or is poorly detailed Documentation always up to date, translated and possibly adapted to different target readers (end user, sysadmin, manager, ...) 1 Quality assurance process No QA process Identifies QA process but not much formalized and with no tool Automatic testing process included in code's life-cycle with publication of results 2 No bug or feature request management tool Standard tools provided (for instance by a hosting forge) but poorly used Very active use of tools for roles/tasks allocation and progress monitoring 2 svn, maven, ant, forge objectweb, jira.org, xwiki.org Packaging for various operating systems BSD The software is not packaged for FreeBSD A port exists but it has important issues or it doesn't have official support A official port exists in FreeBSD 0 The software is not packaged for Mac OS X A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The software is not packaged for NetBSD A port exists but it has important issues or it doesn't have official support A official port exists in NetBSD 0 The software is not packaged for OpenBSD A port exists but it has important issues or it doesn't have official support A official port exists in OpenBSD 0 Linux The software is not packaged for Debian A Debian package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The software is not packaged for Mandriva A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The software is not packaged for Red Hat/Fedora A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The software is not packaged for SuSE A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 Software can't be installed from source without lot of work Installation from source is limited and depends on very strict conditions (OS, arch, lib, ...) Installation from source is easy 2 Unix The software is not packaged for AIX A package exists but it has important issues or it doesn't have official support A stable package is provided for AIX The software is not packaged for HP-UX A package exists but it has important issues or it doesn't have official support A stable package is provided for HP-UX 0 The software is not packaged for Solaris A package exists but it has important issues or it doesn't have official support (e.g: SunFreeware.com ) The software is supported by Sun for Solaris 0 The project can't be installed on Windows A package exists but it is limited or has important issues or just cover some specific Windows release (e.g: Windows 2000 and Windows XP) Windows is full supported and a package is provided 2 There's a zip with mysql tomcat and xwiki bundled together. Exploitability level Difficult to use, requires an in depth knowledge of the software functionality Austere and very technical ergonomics GUI including help functions and elaborated ergonomics 1 No administrative or monitoring functionalities Existing, functionalities but uncomplete and or need improvement Complete and easy-to-use administration and monitoring functionalities. Possible integration with external tools (e.g: SNMP, syslog, ...) 1 Technical adaptability Monolithic software Presence of hight level modules allowing a first level of software adaptation Modular conception, allowing easy adaptation of the software by selecting or creating modules 2 Everything by hand Recompilation possible but complex without any tools or documentation Recompilation with tools (e.g: make, ANT, ...) and documentation provided 2 Any modification requires code recompilation Architecture designed for static extension but requires recompilation Principle of plugin, architecture designed for dynamic extension without recompilation 2 Project's strategy License, only if user wants to become owner of code Very strict license, like GPL Moderate permissive license located between both extremes (GPL and BSD) dual-licensing depending on the type of user (person, company, ...) or their activities Very permissive like BSD or Apache licenses 1 Very permissive like BSD or Apache licenses Moderate permissive license located between both extremes (GPL and BSD), dual-licensing depending on the type of user (person, company, ...) or their activies Very strict license, like GPL 1 Rights held by a few individuals or entities, making it easier to change the license Rights held by numerous individuals owning the code in a homogeneous way, making relicense very difficult Rights held by a legal entity in whom the community trusts (e.g: FSF or ASF) 0 Copyright 2006, XpertNet SARL, and individual contributors as indicated by the contributors.txt. No pratical way to propose code modification Tools provided to access and modify code (like CVS or SVN) but not really used to develop the software The code modification process is well defined, exposed and respected, based on roles assignment 2 No published roadmap Existing roadmap without planning Versionned roadmap, with planning and measure of delays 1 http://www.xwiki.org/xwiki/bin/view/Dev/Roadmap and on Jira Software has no sponsor, the core team is not paid Software has an unique sponsor who might determine its strategy Software is sponsored by industry 1 The unique sponsor is xpernet, but the project is part of ObjectWeb No detectable strategy or strong dependency on one unique actor (person, company, sponsor) Strategical vision shared with several other free and open source projects but without strong commitment from copyrights owners Strong independence of the code team, legal entity holding rights, strong involvement in the standardization process 0

Detail here the platform details and implementation language(s) and its(their) version Detail in the comment section the J2EE or JavaEE specifications used an their versions as well as the supported servers. The web app is not running on this platform Support for a limited number of servers May run on many servers, respects platform standards all servlet containers should be able to run it. It's based on many standard os java library like hibernate, velocity.... 2 Detail in the comment section PHP versions and the supported servers. The web app is not running on this platform Support for a limited number of servers May run on many servers, respects platform standards 0 Detail in the comment section CGI versions and the supported servers. The web app is not running on this platform Support for a limited number of servers May run on many servers, respects platform standards 0 Detail in the comment section mod_perl versions and the supported servers. The web app is not running on this platform Support for a limited number of servers May run on many servers, respects platform standards 0

No LDAP-based authentication available LDAP available but limited (e.g.: group mapping limited, etc.) LDAP is one of the recommended authentication backend 2 No Active Directory based authentication available Active Directory available but limited (e.g.: group mapping limited, etc.) Active Directory is one of the recommended authentification backend 0 Here we do not attach importance on supported databases, please see the storage support section No database authentication available Database available but limited (e.g.: group mapping limited, etc.) Database is one of the recommended authentication backend 2 Does the system support access rights? To control the capabilities (comment, view, edit, delete, compute, script...) of each users on the overall system Feature is not supported, every user has the same capabilities Feature is partially supported, but not fine grained Feature is supported, and the capabilities are exhaustive according to the system capabilities 2 Does the system support user groups and thus, user groups access rights management? To control the capabilities (comment, view, edit, delete, compute, script...) of each users groups? Feature is not supported Feature is partially supported Feature is fully supported 2 Is the web content dividable in subparts, spaces? Does the system support access rights for those spaces? To control the capabilities (comment, view, edit, delete, compute, script...) of each users (and eventually if they are supported, user groups) on specific space/sub-part of the system? Feature is not supported, the system is not divided in spaces Feature is partially supported, but not fine grained Feature is fully supported, and the capabilities are exhaustive according to the system capabilities 2 Host blocking: deny access from IP list Feature is not supported Feature is partially supported Feature is fully supported 0 Blacklist (of known URL, word or content to associate with spam) Feature is not supported Feature is partially supported Feature is fully supported 0 CAPTCHA: to diffenciate a robot from an anonymous user Feature is not supported Feature is partially supported Feature is sully supported captcha is available through a plugin 1 Robots and search engines control features, such as: nofollow (external links tags with rel="nofollow"), delayed Indexing (of search engine, to have time to track down the spam and vandalism). Do Detail in the comment section. No such features Limited features Such features are supported easily do-able 1 Is it possible to create digital cypher (e.g.: GnuPG)? Feature is not supported Feature is partially supported Feature is fully supported 0 Digital watermarking is a technique which allows an individual to add hidden copyright notices or other verification messages to digital audio, video, or image signals and documents Feature is not supported Feature is partially supported Feature is fully supported 0 Digital Restrictions/Rights Management Feature is not supported Feature is partially supported Feature is fully supported 0 Feature is not supported Feature is partially supported Feature is fully supported 0

The data persisted by the software can-be/is stored in (flat) files in the file system. Reminder: here, a higher score does not mean a better product nor the opposite, it really depends on your needs and non functional requirements. The data persisted by the software can't be stored in flatfiles The data persisted by the software can be stored in flatfiles, though it's not the default option The data persisted by the software is only stored in flatfiles 0 The data persisted by the software can-be/is stored in relational databases. Reminder: here, a higher score does not mean a better product nor the opposite, it really depends on your needs and non functional requirements. If the score is 1 or 2, do detail (in the comment section) the supported db (MySQL, PostgreSQL, Oracle, SQLite, other) and their version. The software does not support any relational databases The software supports a few relational databases The software supports all (or most) of the market relational databases mysql is the default but xwiki may run on all jdbc drivers enabled databases. 2 The data persisted by the software can-be/is stored in XML databases. Reminder: here, a higher score does not mean a better product nor the opposite, it really depends on your needs and non functional requirements. If the score is 1 or 2, do detail (in the comment section) the supported db (BerkeleyDB , other) and their version. The software does not support any XML databases The software supports a few XML databases The software supports all (or most) of the market XML databases 0 The data persisted by the software can-be/is stored in object (oriented) databases. Reminder: here, a higher score does not mean a better product nor the opposite, it really depends on your needs and non functional requirements. If the score is 1 or 2, do detail (in the comment section) the supported db (ObjectDB, Versant, Cache, other) and their version. The software does not support any object databases The software supports a few object databases The software supports all (or most) of the market object databases 0 The data persisted by the software can-be/is stored in revision control system. Reminder: here, a higher score does not mean a better product nor the opposite, it really depends on your needs and non functional requirements. If the score is 1 or 2, do detail (in the comment section) the supported db (CVS, SVN, ClearCase, other) and their version. The software does not support any RCS The software supports just one or a few RCS The software supports all (or most) of the market RCS 0 Does the system support data warehousing? This feature doesn't exist The feature exists with limitation (TODO) 0

http://validator.w3.org Page not valid (parse errors) Page not valid with important errors (encoding mismatch) Page valid, or with minor errors (missing "alt" attribute, use of unknown attributes) 2 http://validator.w3.org Page not valid (parse errors) Page not valid with important errors (encoding mismatch) Page valid, or with minor errors (missing "alt" attribute, use of unknown attributes) 2 http://jigsaw.w3.org/css-validator/ CSS doesn't or no valid not valide (parse errors) CSS not valid with important errors (encoding mismatch) CSS valid, or with minor errors (missing "alt" attribute, use of unknown attributes) 2 http://developer.apple.com/internet/webcontent/bestwebdev.htmls HTML tables should not be used for layout/positioning, CSS is there to help HTML tables are not used for layout/positioning Not too much used Systematically, too much used 2 Frame use frame tags are not used frame tags are rarely used Systematically, too much used 2 iFrame use iframe tags are not used iframe tags are rarely used Systematically, too much used 2 CSS designed for printout No Yes, but print-outs are not well rendered for a few use cases. Yes 2 Supported browsers Firefox, please detail the supported version in the comment section Not supported at all Not officially supported, but works ok or good enough Supported and advised browser 2 Konqueror, please detail the supported version in the comment section Not supported at all Not officially supported, but works ok or good enough Supported and advised browser 1 MSIE, please detail the supported version in the comment section Not supported at all Not officially supported, but works ok or good enough Supported and advised browser 1 Safari, please detail the supported version in the comment section Not supported at all Not officially supported, but works ok or good enough Supported and advised browser 1 Legacy browsers are browsers outdated like MSIE4 and Netscape 4, please detail the supported versions in the comment section Not supported at all Not officially supported, but works ok or good enough Supported and advised browser 1 Browser required enablings: Javascript, applet, SVG, and Flash. Reminder: here, a higher score does not mean a better product nor the opposite, it really depends on your needs and non functional requirements. Is the browser javascript enabling required ? If the score is 1 or 2, do indicate in the comment section the required jvm version. If the score is 1, do detail. The interface makes no use of javascript, and thus, does not need javascript to run at full flavor and speed The interface makes use of javascript but can properly function without it. Javascript is necessary to use the interface (beacuse it's AJAX based for instance). 1 Does the browser needs a java plugin (to enable applet) ? If the score is 1 or 2, do indicate in the comment section the required jvm version. If the score is 1, do detail. The interface does not contains any applet, and thus, does not need java to run at full flavor and speed The interface makes use of applet(s) but can properly function without it. A Java plugin is necessary to use the interface, the applets are key players in it. 0 Does the browser needs a SVG plugin ? If score is 1 or 2, do indicate in the comment section the required SVG version. If the score is 1, do detail. The interface does not contains any SVG graph, and thus, does not need any SVG plugin to run at full flavor and speed The interface makes use of SVG but can properly function without it. A SVG plugin is necessary to use the interface, the SVG graph are part of key features of the interface. unless you want to use SVG, it's not required 1 Does the browser needs a Flash plugin ? If score is 1 or 2, do indicate in the comment section the required Flash version. If the score is 1, do detail. The interface does not contains any Flash graph, and thus, does not need any Flash plugin to run at full flavor and speed The interface makes use of Flash but can properly function without it. A Flash plugin is necessary to use the interface, the interface is mainly made of Flash. 0

Is the whole user interface internationalizable? Is Unicode supported? Are Right-to-Left languages supported (as for Hebrew and Arabic)? The feature doesn't exist Limited support Fully supported 2 Does the UI have a complete skin system? (a User/UserGroup customizable interface for instance) The feature doesn't exist Limited support Fully supported 2

This section describes the system's web content/attachement management features. Metadata are information related to a document like (keywords, category, author, copyright holder...) Metadata are all the specific keywords that can be attached to a document (e.g.: sun, holydays, summer for a picture from your last holydays) Can't add specific keywords Keyword can be add but with limitation: limited list, no easy to way extend the list Keyword power are easy to add extend 0 Ability to do a classication in predesigned hierarchy, category or namespaces This feature doesn't exist The feature exists but is limited A new document can quickly be registered in the hierarchy 2 Supported means that the internal engine is able to store and eventually read or parse file content in order to create preview file, find key words, and thus use for search, merge and diff If score is 1 or 2, do detail in the comment section the supported features : parsing, previewing, reading, searching not supported partially: for instance: storing and metadata are supported but parsing is not (and consequently nor preview nor search, diff, merge) fully supported 2 If score is 1 or 2, do detail in the comment section the supported features : parsing, previewing, reading, searching not supported partially: for instance: storing and metadata are supported but parsing is not (and consequently nor preview nor search, diff, merge) fully supported 2 If score is 1 or 2, do detail in the comment section the supported features : parsing, previewing, reading, searching not supported partially: for instance: storing and metadata are supported but parsing is not (and consequently nor preview or search, diff, merge) fully supported 1 If score is 1 or 2, do detail in the comment section the supported features : parsing, previewing, reading, searching not supported partially: for instance: storing and metadata are supported but parsing is not (and consequently nor preview or search, diff, merge) fully supported 1 If score is 1 or 2, do detail in the comment section the supported features : parsing, previewing, reading, searching not supported partially: for instance: storing and metadata are supported but parsing is not (and consequently nor preview or search, diff, merge) fully supported 1 If score is 1 or 2, do detail in the comment section the supported features : parsing, previewing, reading, searching not supported partially: for instance: storing and metadata are supported but parsing is not (and consequently nor preview or search, diff, merge) fully supported 1 If score is 1 or 2, do detail in the comment section the supported features : parsing, previewing, reading, searching not supported partially: for instance: storing and metadata are supported but parsing is not (and consequently nor preview or search, diff, merge) fully supported 1 Format are: WMF, SVG not supported partialy (buggy or limited feature) fully supported 1 The documents targeted by the version control are those listed as fully supported in the above "documentsupport" elements No history/versioning limited number of document revisions unlimited number of document revisions on wiki texts and attached docs 2 No diff feature Revision Diffs with the latest Revision Diffs with the all on wiki texts only 2 No rollback feature rollback to the latest rollback to all on wiki pages only 2 No such merging tools basic merge tools smart merge tools 0 Supported means that the internal engine is able to store and eventually make thumbnail/preview file Format are: JPEG, GIF, PNG, BMP, TIFF, XPM not supported supported fully supported 1 Format are: PSP (PaintShopPro), PSD (Photopshop) not supported supported fully supported 1 The metadata and media content support is to be detailed in the above metadata and mediasupport elements No search engine available Searches are limited (to filename, metadata or text content for instance) Searches are feasable through most of the media content and the metadata the non fully supported format are not parsed in the search 2 This feature doesn't exist The feature exist but is limited. This feature is fully powered 2 No such features recent changes advertised according to the today's date recent changes advertised only changes that happened since user's last visit 1 Do detail the rss feed format/protocol in the comment section This feature doesn't exist The feature exists but is limited This feature exists and feeds are tunable and/or atom feeds are available 2 Do detail the media in the comment section This feature doesn't exist The feature exists for one communication media This feature exists for several media: e.mail, and IM for instance easily do-able but not out of the bow 1 Ability to lock file avoid data lost or synchronization issues The feature doesn't exist The feature just exists The feature exists, and administrator can quickly unlock a file from an user. A time out system exists to unlock file after a certain amount of time. 2 Adding or updating a document in the system may be done through a complex workflow. Do detail in the comment section The feature doesn't exist The feature just exists, but the workflow is simple, a single moderator system for instance The feature exists, and the workflow is tunable. 0 Adequate software architecture for custom plugin creation, easy plugin interface for writing your own additions. Do detail in the comment section the supported plugin languages No such feature limited support fully supported 2 No such feature poor API rich API 2 No such feature limited integration capabilities good capabilities 2 No such feature limited integration capabilities good capabilities 2 No such feature partially or poorly implemented well done 2 No such feature A single blog is possible multiple blogs supported 2 No such feature partially or poorly implemented well done easily do-able but not out of the box 1 No such feature partially or poorly implemented well done 2 No such feature partially or poorly implemented well done 2 No such feature limited integration: tickets linking well supported: tickets linking and metadata extraction easily do-able but not out of the box 1 others: FAQ, meeting minutes, Action Tracker plugin, bookmarklet, Geolocalisation features: GeoURL or googleMaps plugins, Tagging and Tag clouds (delicio.us, technorati, others), etc. Do list the plugins in the comment section. No such feature a few other plugins many other plugins flickr, googlemap, etc... 2

the wiki pages (or documents) can be viewed, created or edited at anytime by anyone from a web browser (with certain limitations for protected areas cf. the websecurity section ). The wiki page are only created and accessible through CamelCase links the wiki supports free links the wiki supports free links and image links 2 Not supported supported : access to a discussion/comment area particular to that page fine grained discussion supported : possible to comment the page by section 1 list of all the existing pages (and pages within the hierarchy, if the hierarchy is supported, cf. webcontentmanagement section) The features does not exists The feature exists but is limited The feature exists and is complete 2 The features does not exists The feature exists but is limited The feature exists and is complete 0 The features does not exists The feature exists but is limited The feature exists and is complete 0 The features does not exists The feature exists but is limited The feature exists and is complete 0 The features does not exists The feature exists but is limited The feature exists and is complete 0 The features does not exists The feature exists but is limited The feature exists and is complete 0 The features does not exists The feature exists but is limited The feature exists and is complete 0 The features does not exists The feature exists but is limited The feature exists and is complete 2

All the pages (or documents) can edited at anytime by anyone from a web browser, (with certain limitations for protected areas cf. the websecurity section ). The following element details the editing features. Not supported, it's not a wiki n.a. supported 2 Not supported limited support: unicode, nor Right-to-Left Support (as for Hebrew and Arabic) are supported fully implemented 2 The following features list is supposed to show the ease of learning and using: writing, reading and modifying wiki pages the most known light weight markup language are : CREOLE (http://www.wikicreole.org/wiki/Home), BBCode (http://en.wikipedia.org/wiki/BBCode), Textile (http://en.wikipedia.org/wiki/Textile_%28markup_language%29), Markdown (http://en.wikipedia.org/wiki/Markdown), BBCode (http://en.wikipedia.org/wiki/BBCode), Radeox API (http://radeox.org/space/start) this wiki has a very specific or very poor syntax this wiki has a uncommon or poor syntax this wiki support a standard and rich light weight markup language 2 not implemented implemented but with a limited API, simple tables only implemented exhaustively, simple and complex (colspan and rowspan) table support 1 not allowed limited support supported 2 not implemented implemented but with a poor API implemented exhaustively 2 not supported n.a. supported 2 support for footnotes, quote, interwiki links, emoticon and other icon rendering through syntax. Do list in the comment section. No such feature a few other syntax/editing plugin many others 2 Does the wiki provides the following features: Preview before saving; Section Editing or whole page only editing; Double-Click on the text to Edit; access Keys (to save, edit, quit ...) ; different editor are supported (some with editing Toolbar); a fully WYSIWYG editor is available. Do detail the available features in the comment section. very limited features a few of those features are available all those features are available 1 Useless feature if you use a decent browser like firefox2 that contains an inline spell checking: a built-in spell checker enables users to quickly check the spelling of text entered into Web forms (like this one) without having to use a seperate application. no spell checker availble or it's just based on a too limited dictionary that make it being a wast of time working dictionnary but limited (e.g: grammar not included, false positive, hard to extend) Powerful dictionary 0 Not supported limited support supported 2 Those features are not that usefull when the pagesversioncontrol is well designed, they can be things like: "Minor Changes flagging" feature, or "Change Summary" features No such feature limited features exhaustive features 0 Design Engine for Meta-Data and Forms, allowing to design custom forms with text fields, textarea fields, number fields, static select fields API to display meta-data in view and edit mode inside the Wiki page. (to create custom forms and templates and In-place (inline) editing of form information in pages). No such feature limited features exhaustive features with a rich API 2 hightlight (colorize) source code snippets when added to a wikipage No such feature present but minimal very well supported: colorize according to code/language specifications 2 No such feature partially or poorly implemented fully supported and standard : LaTeX syntac support: to edit mathematical formulas in Latex syntax directly in the Wiki and display them as images 0 No such feature partially or poorly implemented well done 0 No such feature partially or poorly implemented well done 2 No such feature partially or poorly implemented well done not officially released yet 1 support for Image Editing (applet for instance) or other media in-line editor (SVG, MindMap ...) No such feature one or two editing capabilities like these many capabilities svg and mindmap in progress 1 programming API to create custom dynamic web applications only using the Wiki interface. Do detail in the comment section the supported wiki scripting languages. No such feature limited API rich API groovy and velocity script ability 2

RSS feeds are already described in the webcontentmanagement include/section. Here we list the other export kinds. No such feature limited support fully supported 2 No such feature limited support fully supported 2 No such feature limited support fully supported 2 No such feature limited support fully supported a bit buggy 1 No such feature limited support fully supported in progress 1