Search: concept

not be perceived different than a standard website (the concept of space and wiki should be transparent

not be perceived different than a standard website (the concept of space and wiki should be transparent

2.0 modularized concepts, added explicit extensibilty, and removed major pain points of 1.0

be introduced. In the code, there actually exists the concept of a syntax in which translations are written

to specify the syntax should be introduced. In the code, there actually exists the concept of a syntax

comment : There is not much about the changes in database schema and how to limit extensions broken by the removing of space concept.

comment : I think this a regression from a user POV. A folder or a nested documents concept seem more intuitive.

not lose Actions we should deprecate the "Space Administration", since the "space" concept have

", since the "space" concept have to disappear from the UI. == Constraints === * we should be able

mails : * [UX] Wiki - Space - Page concepts pitch http://markmail.org/thread/7y62ewmo2ltdeomq (Jul 31, 2014)

Problems UC1: Users don't always understand the Nested Pages concept. They are lose because they know the concept of Folder and Files and they are used to it, and then we ask them to switch to something new that breaks their habits. UC2: Users often needs a page that will be the container of some

{{toc/}} = Problems = * **UC1**: Users don't always understand the Nested Pages concept. They are lose because they know the concept of Folder and Files and they are used to it, and then we ask them to switch to something new that breaks their habits. * **UC2**: Users often needs a page

Concept I propose to improve the color theme editor to make it more powerful and flexible. In order to achieve this, I propose to: Add a new tab "Customized Variables" to the editor. This tab would allow us to add more LESS CSS variables and list them in a list We could use

== Concept == I propose to improve the color theme editor to make it more powerful and flexible. In order to achieve this, I propose to:\\ * (% style="line-height: 1.4em;" %)Add a new tab "Customized Variables" to the editor. This tab would allow us to add more LESS CSS variables and list them

XWiki Help Desk Data Model Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. Issue Title Description Language

= XWiki Help Desk Data Model = Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. |=Issue |Title

P1: Keep the current home page with some improvements that we have been discussing for a while. a) Improve the welcome message displayed by Main.Welcome to focus on wiki concepts. Maybe on the lines of what we have already discussed in the past This hopefully fixes UC1 b) Fix welcome gadget editing

P1: Keep the current home page with some improvements that we have been discussing for a while. a) Improve the welcome message displayed by Main.Welcome to focus on wiki concepts. Maybe on the lines of what we have [[already discussed in the past>>http://design.xwiki.org/xwiki/bin/view/Improvements