In fact, when you export an xwiki page (to export a .xar file, or to put this page under source control, etc), it is represented as an .xml file. This file contains the markup (in any syntax chosen for the page), and some other information, like author, dates, other xwiki stuff possibly (xobjects, xclass etc) that may not interest you at first. Concept is that you can then re-import this xml file in any xwiki instance, and it will create the exact same page you exported. Usually we put a number of those files in a .xar file, allowing to import or export a bunch of pages at once.
What propose the SVN and the Github apps, are ways to synchronize your wiki pages, from your running xwiki instance on one side, and a github or svn repo on the other side (under the form of those .xml files). As far as I know, this synchronization is not automatic: - when you click "commit", it will push changes from the running xwiki instance to source control - if you set a CI server watching modifications of source control, you can rebuild upon a change in markup in a page - when you click "update", it will pull changes from source control into running xwiki instance - if you refresh a page for which .xml was changed and pulled, html of course is refreshed. I don't know much more as I never used those apps, so please extension creators correct me if I'm wrong :) About editing directly those exported .xml files : it is possible but not recommended as format is not so readable, some parts are binary, and others are xml-encoded (so if you forget to xml-encode your modifications, you generate pages impossible to import back in xwiki). Hope this helps, Jeremie 2014-10-23 15:21 GMT+02:00 Yves Moisan <yves.moi...@mondoin.com>: > Hi Paul, > > I thought the markup files (XWiki pages == markup files ?) alone were > versioned -- at least that's how I figured the SVN Application plugin > worked. I was thinking something along the lines of what ReadTheDocs > offers for GitHub users, that is automatic build of the documentation upon > a change in markup )in taht case markdown or reStructuredText), only in the > case of XWiki I thought just updating the source underneath would > automagically render in HTML upon page refresh, sort of. > > I realize I need to understand a bit more on how XWiki works. > > Thanx for your input, > > Yves > > Yves, >> >> this is related strongly to the layout of source code for XWiki pages. >> It has been discussed over and over but has not come to a final agreement. >> I still feel it is not sane to edit the XML files of the xar exports. But >> that is what most people still do, in that they export it (without looking) >> into the source trees, and import it. >> >> I still find we need to devise some best practice there. >> >> paul >> > > _______________________________________________ > users mailing list > users@xwiki.org > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
