On Thu, Jan 13, 2011 at 09:23, Vincent Massol <vincent(a)massol.net> wrote: We can always fallback to page name, why adding a constrain where none is required ? 2) Should we merge page names and titles in the UI (ie only expose titles I do not think so, I see page names as URL and title as pretty names or the like. So completely hiding page names is not so good, since being able to choose URL is a feature. I think we should be keep both and be able to help generating page names and hiding page name as much as possible (since these are at least in URL) for those who should (viewer) or would (lazy editor) not care about it. I do not like generated titles, since these are difficult to manage and even cause confusion. When the UI has been changed to display the title, we have had the double title issue, and we had to hack for fixing it. This have obviously failed in some cases, and I have edited many pages to fix such issue. So, no I do not think title should be generated, but that title should fallback to page names. This is really useful for applications to dynamically generate titles. On the other hand, it add a high level of complexity since title may depend on the way a page is opened, something that defeat the usage of titles in navigation panel for example. There is also other options,why not allow applications to overwrite a static title while the page is displayed, and use the title (static) when referencing to the page from other pages. - Jérôme has started discussing pretty names for Spaces, and this could be closely related to titles. - Usage of titles should be discuss as well, since these usage may cause some constrains to the way we could implements titles. Do we want title in navigation, links, breadcrumbs, .... ? I think the answer is Yes, and to perform these properly we may need a title cache or to constrain title to be almost static. I am in favor of static titles since it will cause less confusion and is more in the idea that titles are pretty names for pages. Hope this open the discussion in a good way. Denis -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

Hi, Having page name and page title is VERY disturbing for end users. We should in one way or another merge (not make accessible for end user) page name and page title. IMO this is a major usability concern. I logged a jira for the purpose: XE-907 see below. On Thu, Jan 13, 2011 at 9:23 AM, Vincent Massol <vincent(a)massol.net> wrote: For content pages, it does not make sense to have a page without a title (it is like someone with no name!). And since we don't have page type feature I guess the answer is "title should be mandatory" for all type of pages. This is needed. If we don't want that for all users we could enable page name and page title separation based on user type. If we choose 1) then I would say that page title should be input by user and not generated. As you say, we are already able to type velocity syntax in page titles which is enough IMO. Unless there is use case to illustrate wiki syntax in page title, I am not sure we should work on that. Just like Denis mentions, space pretty name is closely related to this topic. Application Within Minutes also has some topics with page names.