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

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

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

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

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

that should be gardened based on a given concept. For example, a script fetching every document updated

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

relate artefacts with one another: * RDF proposes the concept of triples: subject - predicate - object

]], either from a tuple of its component fields. = Concepts = Similar to the [[authorization API

of abstraction on top of the existing XWiki concepts, there is no new implementation of the rights

, but those concepts are internal details from the pov of this API and should never be a concern of the caller