Re: [xwiki-users] Idea collection minimal xwiki configuration

Hi All, First of all thanks for all the replys filled with helpful advices, this is greatly appreciated, I will try out the solutions the next days an post feedback. Second, I must have misunderstood the point, sorry for this, I think Caty was right there first of all stating the points I made where very specific, this is true and does not make any sense to use for a simplify my wiki page. I think the Extensions Manager in XE 3.2 sounds good, since it gives users the choice form scratch to define some complexity., I will Install and try it out ASAP and give feedback.

I think it would be good to have examples in the wiki as well, lets take the forms, the page http://platform.xwiki.org/xwiki/bin/view/Features/Formsexplains how to do this, but it would it not be far easier to have one or two forms already build in, that users can than adapt, personalize, like with the panels? Is this possible or are forms to individual? The flavors idea sounds good, I was not aware of this before, we should look at the needs for each config indeed I believe the categories provided by Sergui suffice. Thanx again for the feedback, I will go and try out all the advices now… Wouter On Fri, Sep 9, 2011 at 4:51 PM, Vincent Massol <vincent(a)massol.net> wrote: > Hi Wouter, > > On Sep 8, 2011, at 11:04 AM, Wouter de Vos wrote: > >> Hi Users, >> >> After some mails with Vincent and Scott the idea was born to make a >> strip-down-xwiki guide. >> The reason for this is the fact that for a lot of novice users, xwiki > seems >> at the first glance to complex to handle. >> By making a strip-down Guide we hope to make Xwiki more accessible for a >> broader audience, and thus generate more users worldwide. >> >> In order to make this strip-down Guide as complete as possible, I would > like >> to ask all of you to post your thoughts and ideas on this. >> For starters, here are mine, if they are allready easily solved, let me >> know: > > I wasn't expecting this kind of feedback. For me the idea of this thread > was to discuss things that the user could want to hide. A lot of what you > mention isn't about hiding. Let's take them one by one. > >> -Make the search function easier to adapt. >> For instance, I have multiple spaces, and i want that the search function >> only searches in certain, predifened spaces and shows the results within > the >> space the search was started from. > > This isn't about hiding. The search can already filter the spaces to search > into (there's a combo box on the search page for that. Can you tell us > precisely what doesn't work with the current solution? > >> -An easy way to create a template so that users cannot copy paste in >> whatever form and shape they want, but it shows a line where they can > type >> in the header, and below the content. All in the same style. > > I'm not sure what you call "template". > > We already have the notion of page templates, see the Administration > application documentation on extensions.xwiki.org. > >> -An easy way to show-hide the comments box on the bottom of the page. At > the >> moment I use a solution where I include a document with the script to do >> this in, in every page. This should be dealt with globally, and possible > for >> people without a lot of programming knowledge. > > Yes we need this. The solution to this is what Marius is currently working > on in the context of App Within Minutes, i.e. the ability to specify for any > page what sheet it uses to display its content. Marius can probably > elaborate more on this. > >> -The sandgrains work, but not from one space to another, at the moment I > use >> the include Makro to maintain my saindgrain navigation intact, but it > would >> be far easier if documents from other spaces where I link to, adapt the >> parent from the space where I started from. > > I have no clue what sandgrain means. What is it? > >> -The Logo has a predefined link to the main wiki, > > Not true. It has a link to the current wiki. > >> which causes endusers in a >> space, when they click on this, to get to the main wiki page, and it >> confuses them. I would like an easy way (not by editing the global.vm >> template!) to personalize this. > > I'm not convinced at all by this. I think you might be wanting to use XEM > instead of XE since you seem to be using spaces to completely segment > projects. Please confirm. > >> -A wide spread opinion says, that you can just give users rights to > certain >> documents. > > I don't understand why you're talking about opinion and widespread. This is > well documented. > >> But if an enduser can see a document, but not open it, the >> endusers feels as if there are secrets kept from him. > > Well that's exactly what it is about! Putting rights so that only some > people can see some documents means keeping secrets inside so that others > don't see them. Otherwise just use the default right which is wiki-oriented > and which allows people to view/edit all documents… ;) > >> I want an easier way >> to hide these documents completey, but show them to other users who are >> allowed to see them in the same space. > > Yes. It's a big change to do but we already discussed this in the past and > agreed that document names shouldn't be visible when the user doesn't have > view rights on the document. There might even be a jira issue about this but > I can't find it. You could create a new one so that we remember it. > >> -Expand and collaps user generated panels >> If I create panels, their initial state is allways open, I can close > them, >> but when I go to anothere page, it shows the panels open again. Is it >> possible to make check box within each panel in the panel wizard that > allows >> me to change this? > > I thought this was already implemented using cookies but can't find it > anymore in the code. > > Found this in jira: > http://jira.xwiki.org/jira/browse/XE-325 > http://jira.xwiki.org/jira/browse/XWIKI-1308 > >> Many of these points here may seem irrelevant to many of the longtime >> developers, but a lot of questions within this userlist have to do with > the >> usability. >> For your understanding, I come from a total different corner then most of >> you. I come from CM, not from programming. >> But I think if we can work together on this, Xwiki will gain more users > in >> the end. >> If anyone sees this different, let me know, lets communicate so I can > start >> working on the Strip down Guide. > > These are interesting questions but I had a different vision for the strip > down guide. My idea was only to list ways to hide/remove parts of the > default UI. > > I think what Caty mentioned in her response email s interesting, i.e. > defining some flavors precisely in term of both UI and extensions they > should contain. > > Thanks! > -Vincent > >> And to all you programming masterminds out there, keep up the great work, > it >> made Xwiki to that what is today, thank you so much for all the efforts. >> >> With Kind regards, >> >> Wouter