retro-compatibility with many existing features and applications we had to keep the concepts of "Page

the introduction of the Nested Pages concept (in 7.2), the content in a wiki was organized like this: we had some

, this relationship is crucial. The introduction of the Nested Pages concept In XWiki 7.2, due to frequent users

the concepts of "Page" and "Space" in XWiki while adapting them to emulate the Nested Pages feature. Here's

the introduction of the Nested Pages concept (in 7.2), the content in a wiki was organized like this: * we had

, this relationship is crucial. === The introduction of the Nested Pages concept === In XWiki 7.2, due

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

resources and representations "An important concept in REST is the existence of resources (sources

://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request

resources and representations = "An important concept in REST is the existence of resources (sources

/xwiki/bin/view/Extension/Job+Module#HUseanexistingjob so the concepts (job type, job request

precisely, through the concepts of UI Extension Points/UI Extension, it allows Skins (and any Extensions

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

concept of references. |##type##|yes|document|document|The type of the entity. This parameter is also

(By.linkText("XWiki's concept")).click(); } } {{/code}} == Example 2: Choosing Container + DB