Changes for page Architecture

Last modified by Simon Urli on 2023/10/10

<
From version < 20.3 >
edited by Steve Nieves
on 2018/07/30
To version < 21.1 >
edited by Steve Nieves
on 2018/07/30
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,7 +17,7 @@
17 17  This approach has several advantages:
18 18  
19 19  * Works from day one, immediate feedbacks
20 -* Iterative, Need-based development: You have something working from day one and you can have users using it right away, and modify it as you see needs emerge or user request features, at the rhythm you wish.
20 +* Iterative, Need-based development: You have something working from day one and you can have users using it right away, and modify it as you see needs emerge or as users request features, at the rhythm you wish.
21 21  * Continuous Delivery: Tuning it, adding new modules, removing some other, are all operations that you can do live on a running XWiki. Of course you could have 2 XWiki instances: a staging one and a production one, and copy from one to another if you want to control your changes (and put changes in a SCM).
22 22  * Work collaboratively on creating applications: Since everything is done in wiki pages, designers can style while devs create logic.
23 23  * Efficient: what you get with XWiki is akin to what you get when you edit content in a WYSIWYG editor: fast productivity since you immediately see the results of your actions (no need to compile, deploy, etc).
... ... @@ -34,7 +34,7 @@
34 34  * An XWiki runtime is thus made of Core Extensions + non-Core ones.
35 35  * A set of Extensions working together to achieve a goal is called a Flavor.
36 36  * XWiki Standard is a generic Flavor that allow users to collaboratively author content.
37 -* There are 2 types of Extensions (and it's possible to extends Extension Manager to support other kinds):
37 +* There are 2 types of Extensions (and it's possible to extend Extension Manager to support other types):
38 38  ** Extensions containing wiki pages. They are packaged as XAR files (a ZIP file with some metadata).
39 39  ** Extensions containing Java classes. They are packaged as JAR files.
40 40  * An Extension can depend on other Extensions. A Flavor is itself a top level Extension that depends on several other Extensions.

Get Connected