Search: concept

some simple steps, you can implement them in an adhoc way using [[XWiki's concept of Classes

answer : Starting with XWiki 7.2, XWiki supports the concept of [[Nested Pages>>Documentation.UserGuide.Features.ContentOrganization.WebHome]]. There's an extension available called the Nested Pages Migrator to help you convert Terminal pages (i.e. pages that cannot have children) into Nested Pages. You should check the [[Nested Pages

uses the concept of Spaces. However to make it simpler for users and since we introduced the [[concept

of installed applications to the "Flavors" concept. In XWiki, a flavor is simply a bundle of extensions

this new concept. For more informations, do not hesitate to check out [[Caty's blog post>>Blog.XWiki

content : With the release of [[9.5.1>>Download.DownloadVersion||queryString="projectVersion=9.5.1"]] we have dropped the XWiki Enterprise distribution and instead we exposed the [[Flavor mechanism>>xwiki:Documentation.UserGuide.Features.Applications||queryString="#HFlavors"]]. For those unfamiliar with the concept, a "flavor" is a collection

a completely new Skin. More precisely, through the concepts of UI Extension Points/UI Extension, it allows

reading ~-~- what a concept (I'm impatient sometimes). Tom

using Annotations as explained above. == Namespaces == Component API comes with "namespace" concept

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

="HWYSIWYGeditingmode"/}} = Setting the page parent = {{version since="7.2"}} The concept of setting the page parent

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

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

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