Hi, On 24 Oct 2014 at 21:18:31, Eduard Moraru ([email protected](mailto:[email protected])) wrote:
> Hi, > > 2 new proposals (P6 and P7) have been made recently. I did not yet get the > chance to add comments/analysis on them. Feel free to do it in the > meanwhile if anybody wants to. > > A few notes on Jeremie's "Proposal7: DistrbutionWizard sets the homepage of > a flavor and the Help App teaches users" [2]: > > Personally, I find it a rather elegant solution based on separation of > concerns. However, you need to be aware that it is a medium/long term > objective. > > The way I understood it is that we delegate the task of choosing a homepage > to the DistributionWizard that will most likely be in charge of offering > the user flavor options. At that point, the homepage of the current wiki > will be the homepage of the user selected flavor. Optionally, we can also > propose to use a blank page as homepage if the user wants, however this > might be a bit of an overkill, since the user can easily edit the page and > trash everything. The DW should not know at all about any page. It should be up to the flavor to define the wiki pages it will contain and install. Each flavor should propose its own home page. BTW there’s also another variation for the home page that hasn’t been discussed yet: * Make the home page special by not making it editable (and without any docextra tabs at the bottom). So no rollback issue/edit weirdness. * Only admins can change it and only through the Admin UI (basically decide which space home page to display on the wiki home page). * Somewhere in the content of the default home page or through the first time wizard, direct the users to the Sandbox page to try it out editing (since this is what Sandbox is for!) Thanks -Vincent > The task of teaching the user is delegated exclusively to the Help > Application, with the note that the application will also be proposed to > the user to be redirected to, as a final step in the DW (after the > installation of the user selected flavor is complete). > > All of this assumes that we have a properly working Flavors feature and > Help Application. However, what should we do in the meanwhile for the > default XWiki Enterprise UI / Flavor / build? Should we postpone yet again > any work on the homepage until we have the needed elements to delegate the > problematic aspects, or should we do something about it in the meanwhile? > > Thanks, > Eduard > > ---------- > [1] http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageProposals > [2] > http://design.xwiki.org/xwiki/bin/view/Proposal/HomepageProposal7DistrbutionWizardsetsthehomepageofaflavorandtheHelpAppteachesusers > > On Tue, Oct 14, 2014 at 12:40 PM, Guillaume "Louis-Marie" Delhumeau < > [email protected]> wrote: > > > Hello. > > > > I have again a new argument against using the dashboard and the include > > macro in the main page. > > > > When the user uses the "Inline" editor to change some gadgets, she can not > > use the rollback action of the main page to cancel her changes. She has to > > go to the Dashboard page first, and then rollback her changes from there. > > > > Having an include macro in the default page is absolutely not intuitive, > > even if you make it appears more clearly. > > > > Thanks, > > Guillaume > > _______________________________________________ > > devs mailing list > > [email protected] > > http://lists.xwiki.org/mailman/listinfo/devs > > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
