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: * XWiki

-USI-1.2.ppt} which explained the concept of Wiki 2.0 (a.k.a Structured Wikis or Application Wikis

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

(Credit goes to Drupal). XWiki is quite a foreign concept to many people. e.g. people who

, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions

* Knowledge of CSS\r\n* Knowledge of LESS\r\n* Knowledge of Git\r\n* You will encounter concepts like XWiki

will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular

/task/6056420625612800/]]). XWiki is quite a foreign concept to many people. e.g. people who

bring bugfixes but it also come with a new rendering Syntax variants concept and new experimental Live

with a new rendering Syntax variants concept and new experimental Live Data tools (but not used in

rather than the domain concepts users have in mind. We are using wikis as a platform for empowering end

concepts users have in mind. We are using wikis as a platform for empowering end-users to perform

on unix or <tomcat home>/logs/catalina.out for Tomcat. Job Logs XWiki has the concept of jobs (e.g. when

== XWiki has the concept of [[jobs>>extensions:Extension.Job Module.WebHome]] (e.g. when you install

(By.linkText("XWiki's concept")).click(); } } {{/code}} == Example 2: Choosing Container + DB

Concept This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: wiki pages (*.xml files) velocity templates (*.vm files) Strategy Specifically the idea is to be able to write integration tests that use the real code except

{{box cssClass="floatinginfobox" title="**Contents**"}} {{toc/}} {{/box}} = Concept = This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model. Namely, it focuses on testing: * wiki pages (##*.xml## files) * velocity templates (##*.vm## files) = Strategy

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

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

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