Search: concept

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

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

creators. == Detailed Explanations == Before the introduction of the Nested Pages concept (in 7.2

concept === In XWiki 7.2, due to frequent users demands, we have introduced the ability to create spaces

that Nested Pages are emulated using Nested Spaces. This is why the concept of Nested Spaces still exists

Nested Spaces. This is why the concept of Nested Spaces still exists. = Migrating to Nested Pages

we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Pages. We've also decided to drop the concept of Parent

inside other wiki pages. More specifically we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Pages. We've also decided to drop the concept of Parent/Child relationship since it was too complex for end

basic help concepts. The left panels area also showcases now the 'Navigation' panel, while the right

basic help concepts. The left panels area also showcases now the 'Navigation' panel, while the right

concepts. The left panels area also showcases now the "Navigation" panel, while the right panels area

missing begin/end event on document locale and revision so input filter for which those two concept don't

also benefiting from some basic help concepts. The left panels area also showcases now the "Navigation

missing begin/end event on document locale and revision so input filter for which those two concept don't

to compile, deploy, etc). General Architecture Architecture Concepts: XWiki is a webapp that is deployed

actions (no need to compile, deploy, etc). = General Architecture = Architecture Concepts

to create wiki pages inside other wiki pages. More specifically we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Documents. We've also decided to drop the concept of Parent/Child relationship since it was too complex

Wizard. Also note that since this version introduced the concept of Nested Spaces and Nested Documents

we've decided to drop the concept of Space in the UI (it's still there at the API/platform level) and instead, to replace it with the concept of Nested Documents. We've also decided to drop the concept

will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find

the Class Wizard app and it has detailed the concepts of classes, objects and properties and introduced

in documents. You can use these basic concepts to build custom applications at the document or presentation

, this tutorial will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you

and it has detailed the concepts of classes, objects and properties and introduced the authoring templates

. You can use these basic concepts to build custom applications at the document or presentation layer

will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find

the concepts of classes, objects and properties and introduced the authoring templates and page design sheets

concepts to build custom applications at the document or presentation layer of XWiki without having

will introduce the concepts of Authoring Templates and Page Design Sheets, patterns that you will find

and it has detailed the concepts of classes, objects and properties and introduced the authoring templates

. You can use these basic concepts to build custom applications at the document or presentation layer

for which those two concept don't make sense don't have to send them anymore. Instance Output Filter now use

locale and revision so input filter for which those two concept don't make sense don't have to send them