Hello Chris, I think most of these things will require some development but with XWiki scripting support and API it should be minimal in most cases. Chris Haynes wrote: We don't have a JAAS authentication implementation. To support it you will need to implement XWikiAuthService. http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-core/src/main/… There is an interface XWikiGroupService http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-core/src/main/… Another option might be to mirror the users and groups from the database into XWiki using script. Again you could implement the right service or use script to mirror the permissions from the database in the XWiki system. http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-core/src/main/… If the modules are each kept in a separate space, you can set permissions on each space so we can call this "supported out of the box". Each page also can have a "parent page" and you can list all children of a given page. This could be used to represent chapters. Not supported, changing it could be done with script, the easy way is to use plug in rendering transformations. I don't know much about this topic, maybe others can respond? We have an activity stream which records such data but I imagine you want it in a certain format. You could collect the data from the activity stream table or on your own by modifying a velocity file such as view.vm in the webapp folder. You can write a special XWiki document with script to supply the data on request then get the rendered content using XML-RPC, or plain HTTP. We also support Rest and WebDav but I don't know that they can be used to get rendered content. Alternatively scripts can make HTTP requests so you could also push the data to the database instead of pulling from the wiki. Less than 20 lines of velocity script to include the content of each page in the space. We do use CSS @media for the printer friendly pages, I'm not a CSS expert so I would approach the problem by trying to pattern match and remove image tags in the script which bunches the documents together. If there's one help button per paragraph then it's easy ;) Seriously though, I think something could be done with Javascript to detect where the user was when they pressed the button. We have an email sending plugin so the help button should be easy enough. Write a script to generate a standard page, include the script in each page. You can create a form which submits back to the same page then get the parameters from the request. Again you get to decide whether you want to push them to the database or have a cron script pull them from storage in the wiki page. I would approach this by running an instance on a desktop computer and importing all of the word documents there. Then you will have XWiki syntax documents which you can save to the live server or you can export and import them. I appreciate your interest, Caleb

On 04/23/2010 09:36 PM, Chris Haynes wrote: Most of the development for a custom wiki is done not in Java, but in scripting languages on top of Java: Velocity, which is a templating language on top of a public API, and Groovy. The XWiki authentication mechanism is modular, and there are already several bridges between XWiki and external credential services. OOB only LDAP is provided, several others are available at https://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/ . I don't think that one for JAAS is already developed, but it shouldn't be too hard to write it. Yep, depends on how far the JAAS integration goes. XWiki does support groups, and it does support retrieving group membership from external source. Aren't access right enough? If yes, then you can query access rights for the current user on different spaces. If you need to do this with different data, then it should be easy to code a small application for this, once you get the hang of how XWiki development works. There are page access rights, space access rights, and wiki access rights. If you split your wiki as one module = one space, this is straightforward. The normal link syntax doesn't do this, but you could write a wiki macro (see http://platform.xwiki.org/xwiki/bin/DevGuide/WikiMacroTutorial ) that does this using a little bit of velocity and the XWiki API. IIRC, OOB, using the activity stream plugin, but with DN to provide a nice UI for viewing the data. If I don't remember correctly, and this data is not already being recorded, it would be very easy (for a Java programmer) to write it using the observation manager. Possible, but no UI for this is shipped by default, although there is an application which does this: http://code.xwiki.org/xwiki/bin/view/Applications/PDFExportPanelApplication WDYM by eye-candy images? The one from the wiki engine (skin), or images introduced by you? You can check how the printer friendly and the PDF export look somewhere on an existing wiki, for example: - http://incubator.myxwiki.org/xwiki/bin/Sandbox/ - http://incubator.myxwiki.org/xwiki/bin/Sandbox/?xpage=print - http://incubator.myxwiki.org/xwiki/bin/export/Sandbox/?format=pdf A bit of DN, mostly gluing existing APIs together: the mailsender plugin, a custom panel with a bit of velocity code, and maybe a bit of javascript to let the student select the section from the current page. It would be a bit harder to identify by paragraph, since by default paragraphs are not identified automatically. Starting point: http://code.xwiki.org/xwiki/bin/view/Applications/SendPageByEmailApplication I can't find it, but I remember there was an application on code.xwiki.org which did something like this. DN, that's a basic application on top of XWiki, easy to write by an experience XWiki developer in a few hours. If you want to import office documents, then you need the office importer. I'm not sure, but I think you can run OO on a distinct machine and communicate with it via the network, if you can't allocate enough RAM for it on the same server as the wiki. A few final remarks: First, although I think that all you need is (easily) possible with XWiki, and the fact that XWiki is a very flexible application development platform will make it possible to extend and add many other features you didn't think of yet, I must ask you if you really want a wiki engine for this. There are open source applications specifically tailored for e-learning, training and courses, the most famous example being Moodle. If you don't need the extra power and flexibility of XWiki, then I'd advise you to consider using Moodle, which probably offers all you specified here OOB or with existing modules. Second, in order to properly master XWiki, you must learn how to write applications inside XWiki. In theory, anything is possible with XWiki, but to really accomplish something good, you must learn about the data model, the public APIs of the platform, how to write scripts, the services offered, development best practices, etc. The documentation is far from perfect, but it's always improving, and currently it's good enough to get you started. The mailing list is a good help after the documentation ends. Third, please don't read this as a commercial push, but just as presenting an option, since there is quite a bit of custom development needed: if you need help with the development or want things done faster, you could contact the main company behind XWiki, XWiki SAS. See http://www.xwiki.com/xwiki/bin/view/Services/ -- Sergiu Dumitriu http://purl.org/net/sergiu/