Update plugin_doc files

Author: cdujeu

core/src/plugins/authfront.webftp/plugin_doc.html

@@ -0,0 +1,5 @@
+<p>
+    See auth.ftp plugin: provide a rich login screen with full connection to an FTP server (host, port, credentials, etc...)
+    and dynamically authenticate these credentials against this server. Coupled with a "Dynamic" FTP workspace, this is used
+    to setup Pydio as a simple WebFTP application.
+</p>

core/src/plugins/boot.conf/plugin_doc.html

@@ -0,0 +1,7 @@
+<p>
+    This plugin is a basic in-file storage for plugins that cannot be stored in the "conf.*" storage. Namely, CONF, AUTH, LOG and CACHE
+    plugins configurations are using this plugin to store their configs. Data is stored in a JSON file on the server.
+</p>
+<p>
+     Additionally, this plugin provides the first-time installer wizard for Pydio.
+</p>

core/src/plugins/core.access/plugin_doc.html

@@ -0,0 +1,4 @@
+<p>
+    Core features for workspace drivers. Most access.* drivers will extend this plugin.
+    It also provides core model classes for Node, Repository, UserSelection, etc.
+</p>

core/src/plugins/core.ajaxplorer/plugin_doc.html

@@ -1,11 +1,11 @@
 <p>This plugin is a generic container for all 'core' configs of the application. It is always loaded, and the associated options are available in the code via ConfService::getCoreConf() method.</p>
-        <p>Main Sections are :
-            <ul>
-                <li><b>Main Options</b><br>Basic options, Server URL should be defined only if it cannot be detected automatically by the server (when behind a proxy for example).</li>
-                <li><b>Sharing</b><br>Outside world sharing options, see also the Plugins > Actions > Share Center for a lot more options about Sharing.</li>
-                <li><b>WebDAV Server</b><br>Enable this allow users to mount their workspace as network drive on their desktop.</li>
-                <li><b>Command Line</b><br>Enable this to boost performances and/or perform requests directly via command line.</li>
-                <li><b>Compression Features</b><br>Default options should be sufficiant, try tweaking if you encounter problems.</li>
-                <li><b>Miscellaneous</b>Other non-classified options</li>
-            </ul>
-        </p>
+<p>Main Sections are :
+    <ul>
+        <li><b>Main Options</b><br>Basic options, Server URL should be defined only if it cannot be detected automatically by the server (when behind a proxy for example).</li>
+        <li><b>Sharing</b><br>Outside world sharing options, see also the Plugins > Actions > Share Center for a lot more options about Sharing.</li>
+        <li><b>WebDAV Server</b><br>Enable this allow users to mount their workspace as network drive on their desktop.</li>
+        <li><b>Command Line</b><br>Enable this to boost performances and/or perform requests directly via command line.</li>
+        <li><b>Compression Features</b><br>Default options should be sufficiant, try tweaking if you encounter problems.</li>
+        <li><b>Miscellaneous</b>Other non-classified options</li>
+    </ul>
+</p>

core/src/plugins/core.auth/plugin_doc.html

@@ -1,3 +1,5 @@
 <p>Generic authentication options that are shared by all Auth plugins. Basically, determine whether users are enabled or not, guest user allowed or not, etc. Edited via the gui (Settings > Core options). Also provides the standard "auth" actions included by these plugins (login,logout).</p>
 
-<p>You can select one or two Authentication plugin instances to provide auth backend to the application. <br>Default starter setup will typically use a unique SQL-based instance. <br>Default enterprise setup will often be composed of a Master / Slave configuration, Master being and LDAP or equivalent directory, slave being SQL-based to store the pydio-created users locally.</p>
+<p>You can select one or two Authentication plugin instances to provide auth backend to the application.
+    <br>Default starter setup will typically use a unique SQL-based instance.
+    <br>Default enterprise setup will often be composed of a Master / Slave configuration, Master being and LDAP or equivalent directory, slave being SQL-based to store the pydio-created users locally.</p>

core/src/plugins/core.authfront/plugin_doc.html

@@ -0,0 +1,5 @@
+<p>
+    Core loaders for "Authentification Frontends". Authfronts are plugins that can "retrieve" a user credential from
+    a specific context, like user/password submitted by login form, key/secret passed through API header, or through standard
+    Basic-http headers, etc.
+</p>

core/src/plugins/core.cache/plugin_doc.html

@@ -0,0 +1,4 @@
+<p>
+    Caching layer for optimizing both plugins/users/workspaces loading as well as files and folders listing via CacheStreamLayer.
+    Unique implementation is currently based on Doctrine Cache module, see cache.doctrine plugin.
+</p>

core/src/plugins/meta.user/plugin_doc.html

@@ -8,5 +8,4 @@
     <li>anything_area : will create a textarea field</li>
 
 </ul>
-<p align="center"><img src="meta-user.png" alt="Sample"></p>
 <p>Warning, this plugin requires a "metastore" plugin to be active to do the actual storing implementation.</p>

core/src/plugins/meta.watch/plugin_doc.html

@@ -0,0 +1,7 @@
+<p>
+    Implements "watch" system for files and folders.
+</p>
+<p>
+    This plugin is using the underlying MetaStore to attach watch metadata to any node of a workspace, and hooks to the nodes events
+    (node.read, node.change) to create and post notifications to the concerned users. Make sure to add a Metastore to the workspace.
+</p>

core/src/plugins/mq.serial/plugin_doc.html

@@ -0,0 +1,4 @@
+<p>
+    Implements internal messaging inside Pydio, and internal interface with Pydio Booster.
+    Messages are both stored in local queues (inside files on the server).
+</p>