On Jun 24, 2013, at 8:50 PM, Vincent Massol <vincent(a)massol.net> wrote:
On Jun 24, 2013, at 8:46 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi,
I think it should since it's the page that serves to define the {{spaces/}} macro.
Similar question for the Main.Activity page which defines the {{activity/}} macro.
If we want to have those pages used by the user as "features", then I think we
should separate the pages: have one page for the macro definition and another page for
using the macro. One reason is that we don't want technical code to be returned by
default in searches for example and if we have a separate page for the macro then we can
mark it hidden and it won't be returned by default in searches. I think we need to
hunt for all pages that return code by default.
Personally I think that Main.Spaces and Main.Activity should be hidden since there's
no navigation leading to them.
WDYT?
BTW Main.UserDirectory is marked hidden even though it's the home page of an app (the
user directory app) and listed in the Applications panel. This is fine with me since
it's not a content page.
So the rule is probably that non content pages should be marked "hidden" by
default and thus Main.Spaces and Main.Activity should be marked hidden.
Do you agree?
If we're careful that should allow us to only return meaningful results in searches
for users by default.