Le 28 mai 2014 15:27, "Guillaume "Louis-Marie" Delhumeau" < [email protected]> a écrit :
Hi.
What about a page like: WikiManager.CreateWiki? It is a technical page, so should it be renamed WikiManagerCode.CreateWiki. But then, the URL will
not
be nice IMO: /xwiki/bin/view/WikiManagerCode/CreateWiki.
Maybe the logic would be to have : WikiManagerCode.CreateWikiSheet WikiManager.CreateWiki CreateWiki is then not technical, but an admin UI.
My application does not handle data (except the configuration), so it doesn't need to be in a distinct space.
That's why I am +0 to make it mandatory for our applications.
WDYT?
Thanks, Guillaume
2014-05-28 15:19 GMT+02:00 [email protected] <[email protected]>:
Hi devs,
Right now our practice in XWiki Platform for the apps we develop is to move to storing all the pages of an app in a single space.
See
http://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPrac... ,
specifically:
“ Generally, put all your pages in a single space dedicated for the application you're developing (e.g. Faq, Scheduler, IRC, AppWithinMinutes, etc). The name must be as short as possible while still being understandable of course and without overusing abbreviations. "
Now there are potentially some use cases that may warrant to have 2 spaces: one for the content documents and one for the technical documents: - ability to easily set permissions on all technical pages so that only a group of person can modify them but allow another group of persons to edit the content pages (e.g. for the Blog application) - easier to remove all the content pages of an app but still keep the app working
So one idea would be systematically have 2 spaces for apps: - one XXX space (e.g. Blog space) for holding content pages - one XXXCode space (e.g. BlogCode space) for holding technical pages
Of course all technical pages are hidden and thus the XXXCode space will not appear in the list of spaces or searches by default.
WDYT? Would you be ok to modify all our existing apps to go in that direction?
Note: A future solution is to use nested spaces but even with nested spaces the need for 2 spaces would be the same. We would just need to make the XXXCode space a subspace of the XXX space (assuming we can set permissions on subspaces ;)).
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs