1 Jul
2015
1 Jul
'15
2:26 p.m.
Hi,
On 30 Jun 2015 at 12:43:03, Eduard Moraru
(enygma2002@gmail.com(mailto:enygma2002@gmail.com)) wrote:
Hi,
Now that we are moving to Nested Documents, there is the question of what
do we do with the existing space and page templates[1]? How do we (still)
display them?
In the new create UI we will be showing just the option to create a Nested
Document, but for advanced users, we might also show the option to create a
terminal document (NS-style i.e. document in a space).
Since a ND translates to a space WebHome in the NS approach (or previous
approach), we could reuse any existing space templates and display them
instead of page templates.
Existing page templates were built with the NS approach in mind and I am
concerned that, until the app that provides them does not migrate them to
space templates (i.e. ND-compatible), we risk breaking their functionality
(?). This might now be valid for page templates manually created by the
admins that might have no issues since they are content focused and not
processed by any application.
Until they are migrated, we could just show page templates only when
creating terminal documents, as an advanced user.
So the options I see are:
1) Show both space and page templates when creating ND and only page
templates when creating terminal pages, hoping most of them will work most
of the time.
2) Show only space templates when creating ND and only page templates when
creating terminal pages, but risk hiding a lot of useful page templates
from regular users which would work most of the time.
My +1 goes to 1).
WDYT?
2 comments:
1) The template feature is to be able to create a new Blog post, a new FAQ entry, a new
Release Notes page, etc. This feature is still valid in NS or ND.
When I create a new Blog post, I don’t need it to be a terminal page and it probably
shouldn’t be. In any case that should be controlled by the checkbox in the Add Page
dialog:
* if the user creates a terminal page then we apply the template to the terminal page
* if the user creates a non terminal page then we apply the template to the WebHome page
that we create
I don’t see any difference from what we do now (except that the create code needs to be
updated to support NS/ND) so I’m probably missing the point :)
2) I agree we should drop the Space Template notion and instead when specifying a template
page, have an option to also copy the children pages. In this manner, when the user does
Add > Page and applies the template we copy the template page + its children. Of course
if the user chooses to create a terminal page then either we refuse to apply the template
or better, we give a warning saying that the children template pages won’t be copied.
Thus for now, the user would only be able to control the name of the parent page he
creates and the children names would be the same name as in the template structure. In the
future we could imagine offering some algorithm to name children pages.
WDYT?
BTW -0 to -1 to show Space template since we’re removing the concept of Space from the
UI.
Thanks
-Vincent
Thanks,
Eduard
----------
[1]
http://extensions.xwiki.org/xwiki/bin/view/Extension/Administration+Applica…