Hi everyone,

I'm following up on a thread started in 2015 about the best practices regarding 
app pages organization:

  - https://xwiki.markmail.org/message/657vcm6ylkz4yytc
  - 
https://dev.xwiki.org/xwiki/bin/view/Community/ApplicationDevelopmentBestPractices

In this thread, the idea of introducing a dedicated common root area for all 
application technical pages was suggested by Denis:

  https://xwiki.markmail.org/message/kk5l3dwjmpfelkzp

I'm wondering why this idea was not pushed further (it's not strictly 
incompatible with the current best practices, but most of the recent 
applications have their top level area, except a few like Notifications or 
ChartJS).

Comparing with how other platforms do is inspirational (Microsoft Windows "Program 
Files" was mentioned in the thread). On Debian, the Maven package is installed in 
/usr/share/maven/ while files used and produced by Maven can be located anywhere. Along 
the same line, I would see as a user and developer experience improvement if we had the 
following structure:

1) Code:

XWiki
|- MyApp
  |- MyAppClass
  |- MyAppSheet
  |- ...

2) Data: the pages created by MyApp could then typically be located by default 
in a MyApp space at the root of the wiki, the user could however choose which 
default space to use, or leave it empty (then the space from where the user 
fires the create action could be used, for instance, or any scriptable rule).

Another issue I see with the current practice (raised by Clément A. orally) is 
that some application names may conflict with names the user would like to use 
for content that is not strictly related to the app. Not necessarily a big deal 
with one thousand of applications, but might become one with more, wouldn't it?

I understand that the layout proposed above would raise technical issues (XWiki 
space permissions for instance, mentionned in the 2015 thread, and others), 
however what's your view on it from a design perspective? (sorry if I 
overlooked strong arguments already expressed against it)

Cheers

Stéphane

Reply via email to