Search: concept

Improve the layout of XWiki's Concept page. Proposal Before After

XWiki.org Concept (2016)

mails : * [XWiki.org] "XWiki's Concept" page improvements http://markmail.org/message/w3dztiourthzgovo (May 27, 2016)

* Improve the layout of [[XWiki's Concept>>xwiki:Documentation.UserGuide.Features.SecondGenerationWiki.WebHome]] page. {{toc start="2"/}} (% class="row" %) ((( (% class="col-xs-12 col-sm-12" %) ((( == Proposal == ))) (% class="col-xs-12 col-sm-6 col-md-6" %) ((( Before [[~[~[image:before.png~|~|style

generic image placeholder - no image provided Platform vs. Standard Flavor? Concepts: 1: XWiki Product

name (ex. "Notification app allows you to ... ") Check Carousel entries Features: Concepts + Bundle Extensions Promote Flavor concept (Generic XWiki + Flavors [there is also the Standard Flavor developed

. Standard Flavor? *** Concepts: **** 1: XWiki Product + several Flavors (+ extensions) **** 2: Generic

. "Notification app allows you to ... ") *** Check Carousel entries ** Features: Concepts + Bundle Extensions ** Promote Flavor concept (Generic XWiki + Flavors [there is also the Standard Flavor developed

:" page : .../xwiki/bin/inline/Blog/Commuter+Train+Morning+Work For not IT users, the Parent concept

) further introduces the concept of shareable nodes which allows multiple paths of access to a node

the concept of journaled listeners which can ask the repository to re-play all events after a certain

. JSR283 hence introduces the (optional) concept of shareable nodes. This allows implementing multiple

://whiteboardjunkie.wordpress.com/2008/11/24/where-am-i-using-jcr-and-why/] * JSR 283 (JCR 2.0) further introduces the concept

navigations through content * JSR 283 further introduces the concept of journaled listeners which can ask

) concept of shareable nodes. This allows implementing multiple URIs for a given model object

is considered deprecated. This brainstorming wants to tackle again this concept but a bit different

in Administration, Profile, Search, etc. Applications are becoming a major concept inside XWiki and needs

is considered deprecated. This brainstorming wants to tackle again this concept but a bit different

in Administration, Profile, Search, etc. Applications are becoming a major concept inside XWiki and needs

they are in a timeline than seeing them in a list. Also I don't think is necessary the concept of categories when you

the concept of categories is replaced by multiple calendars.

but not concentrate on supporting page concept in HQL requests. References New typed EntityReferences We need new

is not to write The New Model™ but just to provide to the already existing APIs an easy Page concept oriented

XWikiPage directly expose methods that are not following page concept or that we would want to behave

and Java components but not concentrate on supporting page concept in HQL requests. == References

to the already existing APIs an easy Page concept oriented access. * new com.xpn.page.XWikiPage class used

methods that are not following page concept or that we would want to behave differently for this name

the move of that dashboard as a separate app) * It allowed to more easily implement the concept

concept since people don't know pages can be edited and they are not invited to do it. Adding text

* Problematic wiki concept since people don't know pages can be edited and they are not invited to do it. Adding

Even though the concept is not very wiki-oriented, several users have been asking over the years to have the ability to have personal pages (a.k.a private pages or user space), visible to the currently logged user only (by default), acting as a kind of personal sandbox. Requirements UC1: Available

Even though the concept is not very wiki-oriented, several users have been asking over the years to have the ability to have personal pages (a.k.a private pages or user space), visible to the currently logged user only (by default), acting as a kind of personal sandbox. = Requirements = * UC1