Search: concept

. * Skin extensions sounds like an afterthought. I wonder if we cannot somehow merge the concepts together

. Example to illustrate formentioned concepts. Ex: Ajax request to add and init an object

comment : The combination of *actions* (like <tt>save</tt>) and *request parameters* (like <tt>xredirect</tt>) obviously is a very powerful means to work with XWiki documents. Is there any documentation on that? Where do these concepts belong to in the first place, Struts, XWiki, Velocity or another technology?

", or "1" {table} 1.1 Sample use cases TBD. Example to illustrate formentioned concepts. Ex: Ajax

that represents those concepts. Using bells not set: followed: blocked: custom: Other proposal using volume I (Simon) find the volume concept interesting for notifications since there's a lot of variability

for it) - if the page has a partial/custom filter defined Ideally we need icons that represents those concepts

using volume ==== I (Simon) find the volume concept interesting for notifications since there's a lot

if we cannot somehow merge the concepts together. I guess I'd need to see some examples

keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would

particular keywords. Note: could reuse the "Types" concept here maybe, with a built-in type "SPAM" that would

) This concept is to replace (in a lazy way) initial HTML by a richer HTML. What I mean by richer? In order

, expanding the DocumentName concept) Annotation model changes to store such a reference to a field

? === ==== Solution n°1 : Richer HTML (not used) ==== This concept is to replace (in a lazy way) initial HTML

will be devised (for example, expanding the DocumentName concept) * Annotation model changes to store

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

, PatchId toPatch) /** do we need to introduce a concept of dependencies between patches? */ Iterator

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 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