Search: concept

Basics: XWiki's main concepts

Task 3: Understand XWiki concepts AWM has made it simple to create your first application but it's cheating a bit since it's doing all the work of generating the various wiki pages for you.

:) To do that you need to understand the concepts of XClass, XObjects, XProperties, Sheets and Templates.

Track: Understand XWiki core concepts

= Task 3: Understand XWiki concepts = AWM has made it simple to create your first application but it's cheating a bit since it's doing all the work of generating the various wiki pages for you.

:) To do that you need to understand the concepts of XClass, XObjects, XProperties, Sheets and Templates.

Add concept of image to What's New API

title : Add concept of image to What's New API

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

summary : "Recommended" concept has been added to Extension and Repository API

summary : Extensions now have the concept of supporters and support plans. The goal is to replace the very vague concept of //Recommended// we currently have for a very explicit pledge of organizations and individuals (**Supporters**) to support an extension, and to which extent (**Support Plans**).

The introduction of the Nested Pages concept In XWiki 7.2, due to frequent users demands, we have introduced the ability to create spaces under other spaces. It's the Nested Spaces concept. We suddenly had the ability to create a hierarchy of spaces to organize content.

Indeed, the migrator cannot create nested pages in an old XWiki instance where this concept did not exist! Go to the Extension Manager in your wiki, and install the Nested Pages Migrator Application.

However, in order not to break retro-compatibility with many existing features and applications we had to keep the concepts of "Page" and "Space" in XWiki while adapting them to emulate the Nested Pages feature.

For them, this relationship is crucial. === The introduction of the Nested Pages concept === In XWiki 7.2, due to frequent users demands, we have introduced the ability to create spaces under other spaces. It's the **Nested Spaces** concept. We suddenly had the ability to create a hierarchy of spaces to organize content.

This means that Extension Manager will install all of them by default but optional dependencies won't have any impact on the validity of the extension: if the optional dependency install plan fail the extension is installed without it if the optional dependency is uninstalled it won't uninstall the extension if the optional dependency is missing at startup it won't make the extension invalid Managed dependencies Since 8.1, Extension Manager support the concept of managed dependencies. Its the same idea than Maven's element.

{{/info}} = Managed dependencies = Since 8.1, Extension Manager support the concept of managed dependencies. Its the same idea than Maven's {{code}}<dependencyManagement>{{/code}} element.

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages.

XWiki 7.2 has introduced the concept of Nested Spaces. With this new concept it's legitimate to ask oneself what are the differences between using a (sub)wiki or using Nested Pages

On the contrary, ‘pdf-file’ would mean that we want a ‘file’ variation on the main concept of ‘pdf’. Updating the icon set Removing an icon If an icon does not fit anymore in the current context, it should be deprecated and not fully removed.

Even if the XWiki core Development Team only supports Silk and FA4, we still want to make sure that the proposed icons represent concepts generic enough so that they can be mapped to all or most icon themes that can exist.

Replacing those icons with actual icontheme references is not always easy, because the concept they picture is not always mappable in other icon themes, and there's no easy conversion from Silk to the icon theme.

On the contrary, ‘pdf-file’ would mean that we want a ‘file’ variation on the main concept of ‘pdf’. === Updating the icon set === 1.

Even if the XWiki core Development Team only supports Silk and FA4, we still want to make sure that the proposed icons represent concepts generic enough so that they can be mapped to all or most icon themes that can exist. 1*.

Replacing those icons with actual icontheme references is not always easy, because the concept they picture is not always mappable in other icon themes, and there's no easy conversion from Silk to the icon theme.