Search: concept

Here is an example of the minimum maven builds one should run to check a small change in xwiki-platform-flamingo-skin-resources: mvn clean install -f xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-resources -Pquality mvn clean install -f xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test -Pintegration-tests,docker The changes are related to the concept of panels, so we also build mvn clean install -f xwiki-platform-core/xwiki-platform-panels/xwiki-platform-panels-test -Pintegration-tests,docker If you're creating a Pull Request (PR), make sure you keep a written records of what tests you ran and to indicate them in the dedicated section of the PR template that must be filled up with details about the builds ran and the tests passed.

Since these 2 projects contain libraries that are independent of the concept of wikis, this makes it very easy for everyone to use them in their own projects.

The changes are related to the concept of panels, so we also build ##mvn clean install -f xwiki-platform-core/xwiki-platform-panels/xwiki-platform-panels-test -Pintegration-tests,docker## If you're creating a Pull Request (PR), make sure you keep a written records of what tests you ran and to indicate them in the dedicated section of the PR template that must be filled up with details about the builds ran and the tests passed

. == Best Practices == * ((({{version since="11.3RC1"}}There's now the concept of a Syntax Registry and new Syntaxes are expected to register themselves in that registry.

Cette presentation apporte un peu de nouveautes en proposant un runtime web de prototypage ce qui est un concept nouveau et interessant de connaitre pour tout bon developeur ou architecte java.

Utiliser un plate-forme de wiki est très similaire dans son concept à utiliser un serveur d'applications. Tout comme les serveurs d'app offrent des services techniques aux applications hébergées, une plate-forme de wiki offre des services de plus haut niveau tels gestion de contenu, moteur de rendu, stockage, éditeur WYSIWYG, gestion des utilisateurs et beaucoup plus.

You could even argue that traditional wikis are loosing traction or mindshare. Other concepts have arisen in the past such as CMS (Content Management System) and WCM (Web Content Management).

description : Le concept de Long Tail introduit par Chris Anderson est maintenant bien connu dans le domaine du livre. Ce concept existe également dans le domaine des apps.

Getting to know XWiki Track 1: Understand XWiki concepts of XClass & XObjects Track 2: Extend your application Track 3: Styling XWiki Start contributing Track 4: Report or find an issue Track 5: Contribute to the core Future tracks to document: Track: Interactivity in XWiki (JSX, WebJars, Special CSS classes, Front-end Resources) Track: Contribute to an existing extension Track: Contribute a new extension Track: Add translations Other resources: Getting started with XWiki for extension developers.

= Getting to know XWiki = * Track 1: [[Understand XWiki concepts of XClass & XObjects>>TrackXObjects]] * Track 2: [[Extend your application>>TrackMacro]] * Track 3: [[Styling XWiki>>TrackStyling]] = Start contributing = * Track 4: [[Report or find an issue>>TrackIssues]] * Track 5: [[Contribute to the core>>TrackCore]] Future tracks to document: * Track: Interactivity in XWiki (JSX, WebJars, Special CSS classes, Front-end Resources) * Track: Contribute to an existing extension * Track: Contribute a new extension * Track: Add translations Other resources: * [[Getting started with XWiki for extension developers>>doc:Drafts.GettingStartedWithXWiki]].

The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.

Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.

The initial prototype is promising but wil need work to allow concurrent access and faster handling of big volumes of data. Currently the concept is ongoing translation. Reimport of the main language (english) file can be done regularly.

Once it is loaded on launchpad.net there is a quite extensively developed translation application. The concept seems to work by application version. We need to verity if this is the way we want it to work.

profile : * Java proficiency * Familiar with unit testing concepts and best practices * Familiar with functional testing concepts and best practices ** Experience with Selenium and the [[Page Objects>>url:https://code.google.com/p/selenium/wiki/PageObjects]] pattern is preferred * Familiar with web technologies: HTML/CSS/JavaScript * Experience in (unit/functional) testing a previous open source project is a big plus * Willingness to learn and to improve both him/herself and the project

description : See the [[Configuration API>>Extension.Configuration Module]] for general configuration concepts. == Configuration Permissions == It's possible to implement permission checking for ##ConfigurationSource## properties, to decide who has the rights to view or modify them.

summary : Extra Configuration APIs related to platform concepts (e.g. user references)