Hi Guillaume,
On 3 Jun 2015 at 16:10:36, Guillaume Louis-Marie Delhumeau ([email protected](mailto:[email protected])) wrote: [snip] > On the short run: > > - Hide the notion of space in the UI. > > - Hide the `WebHome` name in the UI. > > - When a user creates a page from the UI, it actually creates a space with > a WebHome. > > - Remove the current parent/child mechanism which is outdated (and > confusing) compared to the new hierarchy. > > > On the long run: > > - Remove the notion of space in the model, and replace it by "nested > documents". > > - Tune the rights system to inherit rights from parents to children. > > > Of course, we can discuss the technical details and the implementation > strategies. But for now, we need to know if you accept the general idea > (nested documents). > > > So, I hope you will like this proposal, and here is my +1. Note: I believe this email could have been a VOTE since it’s a very important concept change and we don’t vote on proposal. Let’s consider it as a brainstorming idea ATM which could lead to a VOTE later on if need be. I’m globally +1 to both hiding the concept of Space from the UI and to later on remove it from the model. Some comments: * Regarding the Nested Spaces proposal, see http://design.xwiki.org/xwiki/bin/view/Proposal/NestedSpaces * About hiding WebHome from the UI. This is something we should already be doing now even without the notion of Nested Spaces. Nothing is preventing us from doing it now. * Regarding permissions, since we want to keep the ability to programatically create pages named other than WebHome for now (till we modify the model) we’ll need to do the following: Do not show the page permission menu entry when a user is on a WebHome page (unless there’s already a Right xobject) * Regarding the current breadcrumb, in order to ease the migration, I’d propose to make it configurable in the config: either to use the old style breadcrumb based on parent/child relationships or the new breadcrumb based on Document References. When the old mode is on, editing a page should show the parent relationship field as now. We have to remember that people switching to XWiki 7.2 will not have deep hierarchies set up on their docs (and not many pages named WebHome). * I think we’ll need to go even more in the direction defined in the “conclusion” section of http://design.xwiki.org/xwiki/bin/view/Proposal/ExtendedBreadcrumb, i.e. ** Just a drawer-menu on the right (as proposed for the Macaw skin) ** A breadcrumb based on Document References (+ possibly the ability to execute some actions at each level) * We should probably keep the notion of Wiki even though it could be argued that wikis could be top level documents with some xobject in them. * Regarding Thomas's comment about creating wiki links, yes we might want to do the following: ** When rendering [[label>>A.B.C]] we could check if a page named C exists and if so link to it. If not, check if a page named C.WebHome exists and if so link to it. Otherwise make it a wanted link (ie display a “?”). This would be a similar logic than for URLs (supporting A/B/C as well as A/B/C/WebHome or A/B/C/) Thanks -Vincent > Thanks, > > Guillaume D. > > > > [1] JCR: https://en.wikipedia.org/wiki/Content_repository_API_for_Java > > > > > -- > Guillaume Delhumeau ([email protected]) _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
