Search: concept

XWiki's Concept

{ background: #fff; padding: 10px; margin: -5px -4px 5px -4px; } .concept strong { font

"}} <div class="row concept"> <div class="col-md-9"> First generation wikis are used to collaborate

Anderson introduced the concept of [[Long Tail>>http://en.wikipedia.org/wiki/Long_tail]]. <p

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

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

the Marketing wiki Points of Confusion 'Wiki'-'Space'-'Page' concept The folder icon used for 'Spaces

to understand the concepts and differences between them When asked to create a page with a certain content, she

and wiki concept Looking for 'New' instead of 'Add' Issues Critical issues Difficult to understand

'-'Page' concept ** The folder icon used for 'Spaces' ** It was not very clear the 'wiki-space-page' hierarchy ** It's not only about the hierarchy, but also difficult to understand the concepts

to the 'Create Wiki' - 'Description' area ** Did the tasks using only page and wiki concept * Looking

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

) 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

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

pages are considered a deprecated concept, so we reduce this feature's visibility Page only rights can

into a single 'Page' category ** Terminal pages are considered a deprecated concept, so we reduce

on the old cache services concepts even all the names changes but the more I'm working with JBoss cache

eviction algorithms concept like JBoss or cache4j do to replace the way restriction like capacity

on the old cache services concepts even all the names changes but the more I'm working with JBoss cache

thinking of introduce eviction algorithms concept like JBoss or cache4j do to replace the way restriction

There are multiple issues where users had problems understand the way we combine interface and content languages. This proposal tries to separate the two concepts: interface language and content language, and contains several display variants. Interface Language is set from Administration

There are multiple issues where users had problems understand the way we combine interface and content languages. This proposal tries to separate the two concepts: interface language and content language, and contains several display variants. * Interface Language ** is set from Administration