summary : Proof of concept for XML based api

used yet) : same concept as include overload at copy but here with a real link. It means when editing

good proof of concept. If anyone is up to writing a cleaner, more efficient version - please do, and

" concept. The format of the namespaces is ##<type>:<id>##. The format of the ##<id>## depend on each

== The XWiki project is older that this component concept and sometimes you can find yourself in code

comment : I am new to the whole wiki concept and am trying to delete a Space - Systems&Infrastructure ? with a question mark appended at the end. I have deleted all the documents inside the space, no luck. Where do I insert this code to delete the space. Do I modify a config or properties file or does

8.1, Extension Manager support the concept of managed dependencies. Its the same idea than Maven's

support the concept of managed dependencies. Its the same idea than Maven's {{code

Server.WebHome]] * [[Extension.Discussions REST.WebHome]] = Concepts = == Discussion Context

the different elements, and to dynamically chose the storage location. To do so, two concepts have been put

adopted the "nested pages" paradigm. It means that you will no longer find the "space" concept in the UI

comment : I second Joris Dirks' comment about multiple references on a page to one single footnote. A method for doing that in Tex is described here: http://tex.stackexchange.com/questions/35043/reference-different-places-to-the-same-footnote. I hope a similar concept of (optionally) labelling and then

that should be gardened based on a given concept. For example, a script fetching every document updated