Search: concept

) This concept is to replace (in a lazy way) initial HTML by a richer HTML. What I mean by richer? In order

, expanding the DocumentName concept) Annotation model changes to store such a reference to a field

? === ==== Solution n°1 : Richer HTML (not used) ==== This concept is to replace (in a lazy way) initial HTML

will be devised (for example, expanding the DocumentName concept) * Annotation model changes to store

architecture using a Component Manager * Each component group (set of components for implementing a concept

:" page : .../xwiki/bin/inline/Blog/Commuter+Train+Morning+Work For not IT users, the Parent concept

:" page : .../xwiki/bin/inline/Blog/Commuter+Train+Morning+Work For not IT users, the Parent concept

|Confluence exports can contain archived documents. XWiki doesn't have a concept of archived document. This

concept of archived space. This parameter lets you optionally import archived spaces  as regular XWiki

find the "space" concept in the UI. Instead, each page has now the ability to have children pages

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

done for links. Live filtering is a nice concept, but in an already JS-heavy interface it's better

longer, specially for power users, but Laurent defended the whole wizard concept by saying

keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would

particular keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would