Re: [xwiki-devs] Home Page - Use cases, proposals, what we have until now and what we want to achieve

Hi, 2014-10-28 21:08 GMT+01:00 vincent(a)massol.net <vincent(a)massol.net>et>: Depends, I was thinking more about a specific event like "flavor installed" or "extension installed" or "wiki installed / updated". I'm not sure to get what you would need to do in this post install script ? But it could be completely "manual" or just a link at the end of DW to some possible post-install stuff (like, consult help, manage home page, etc). I'd like to apologize here because my "proposal" was more an idea than a well formalized proposal, even if it ended up in the list of proposals, it's obvious that it misses some thoughts and clarifications... (I understand your -1). Well, if you consider that current UI of XE is the default xwiki "flavor", this is exactly what it's about when we talk about switching home page easily, isn't it ? We want to let user set a home page that doesn't match the default theme freely. Obviously this default theme is not very "thematic" as it's the default and should be versatile ... Home page matching that theme could still be the mostly recommended choice. BTW a flavor, with such mechanism, could provide several "home page" variants and not only one, depending on the case. If I take the case of a flavor based on the Mail archive (or the mail archive extension alone, say), it already provides different views as the app home page (timeline, livetable, etc). Currently the switch is done through conditional include. Currently that app home page is MailArchive.WebHome, if I could register it as a possible home page template, it would avoid having to rename it "Main.WebHome" to make it a flavor (and potentially destroy existing wiki home page by mistake when you install that extension/flavor), and I could fullfill both installation use-cases (of using it as an app among others in some wiki, and as a wiki-wide-flavor in another wiki or subwiki), from the same xar bundled app. Again, here, I talk about possibilities and use-cases that seem logical or interesting to me if I dig into my proposal, but I really don't know if it's a good path or even a good idea for xwiki - I may not have the big picture :) Also, the proposal certainly does not offer any solution for short-term (if you consider it provides options for long-term ;-) ) There was the side-idea of the proposal (not well formulated, maybe was just in my mind) that this wizard and/or DW could be triggered at any later time by an admin if he wants to replace homepage with some other "default" content. Maybe could be seen as a "personalization" step following a new wiki install or upgrade, but that could be triggered at any later time to "re-personalize" his wiki. I would put this then also as a feature in admin UI. The difference with some other proposals, is that it would not be an action available from the standard UI but limited to a post-install step and the admin UI (not like the variant below). I'm not sure if you talk about an additional option, or an option that would replace the "space /apply template" by a more generic "page / apply template", but I don't think anyway that a page template is the same thing as a home page template (whether it's a space or wiki home page). You'd seldom want to use a blog post as a home page ... In this variant, there's still the question, if applying such template is considered an admin operation or not. If it's an admin operation, you also proposed to start moving those admin actions to the admin UI, which is - sort of - what was my proposal about in first place :) (I didn't talk specifically about admin UI at that time, but about avoiding to crowd standard UI menus with unfrequent/admin operations). That being said I don't think it's an admin action, if you need to protect home page, as an admin you can set specific rights and forbid this "apply template" to people that don't have those edit rights. I'm not sure editing home page and applying a template should really be different in terms of privileges. But applying a template on an existing page or home page, seems to be a rather unfrequent operation.