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
on 2018/07/30
Change comment:
There is no comment for this version
To version 20.4
edited by Steve Nieves
on 2018/07/30
on 2018/07/30
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
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).