, dig around in the logic behind the concept and devise an effective solution that inspires action

by the standard parent / child relation in XWiki. In addition, this macro introduces the concept of

description : This API is made to support the [[Scripting Documentation Application]]. The concept of this API is to provide scripting documentation by dynamically searching the current wiki instance for available bindings. Using the information from Maven pom's, those bindings get linked to their

description : Application that allows to create totems. A Totem is a content composed of several sections and each section contains multiple items. A section can be displayed with different ways according to the concept of displayers (For example : Carousel, Article, image, video, simple text ...etc

://extensions.xwiki.org/xwiki/bin/view/Extension/Model%20Module]] module to understand the concept of references

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

description : {{warning}}This is currently a proof of concept and not yet ready for production.{{/warning}} Inspiration: https://github.com/phillip-kruger/graphql-example It follows the [[Eclipse MicroProfile GraphQL API Specifications>>https://github.com/eclipse/microprofile-graphql/]] using the

and breakages are possible. {{/warning}} = Concepts = By default, when a user selects an event type

description : = Users {{info}}Since 12.2{{/info}} Concepts: * This API is independent from where the users are stored (in wiki pages, etc). This allows plugging other implementations to store the users elsewhere than in wiki pages (the default). * This API supports properties for the Guest

description : API to gather external news related to XWiki. The following concepts are used: * News Source Type: The type of source of news, in the form of a component hint. For example ##xwikiblog## represents an XWiki Blog Application news type (which means getting the news from the RSS feed generated