Re: [xwiki-devs] Application pages layout best practices

Hi Vincent, Hi all, The default implementation I would propose would consist in creating data in the space from which the creation request occurs. Do you foresee some issues with that behaviour? If needed, we could add a field in the TemplateProvider class that would accept a script letting developers or users implement any rule for determining which space should be used. By "this would work only if the app provides a template", do you mean a TemplateProvider? Would this be then that TemplateProviders are not considered as a best practice already? It's different imho because my proposal is that, outside the "XWiki" space, only users would create new spaces, never the applications directly without first asking the user for a space name explicitely. I'm wondering if it's a good idea to reserve a space for data and to have one data subspace per app: first, along the operating system analogy, it's not very common to store files per their application origin basis, is it, or is the analogy irrelevant? Second, the line between what we call "data" and "content" is getting more and more blurry (the Jupyter notebooks, just like XWiki are good examples of this), so the user may end up with page hierarchies that are difficult to understand. Regarding the "XWiki" space, we probably agree that it is meant to be a "system" space, do we? If that's the case, I'm wondering if storing the users and groups in that space is the best option, because they are actually writable data. It's a bit specific since they are transversal, and their classes come with the platform, but it remains writable data. Their code could be located in the XWiki space, but the instances could be elsewhere, in a configurable location. Also, prefixing each user and group page with "XWiki" may not please all developers imho: imagine you develop a Facebook like, should the user wall URLs contain "XWiki"? It's always possible to add URL rewriting rules, but that's more complex. The underlying reason could be brand marketing though, which is important. Following up on the operating system analogy, we could also consider log files (and possibly other aspects?). Even though most of the XWiki logs are currently stored on the file system, that could be interesting at some point to store some of them directly in the wiki for easing their archiving and consultation, couldn't it? In that case, we could also reserve a dedicated root space for them. Having very few top level reserved spaces such as "Logs", "Users", "Groups" (provided their name is configurable, also for localization reasons) might be acceptable, what do you think? This looks powerful, I'm looking into it. Cheers Stéphane -- Stéphane Laurière XWiki – https://xwiki.com