Merge pull request #37 from mandrew/master

Moved user docs into userguide folder to display on userhelp site

docs/en/index.md

@@ -6,56 +6,15 @@ these cannot be publicly accessed via deep linking. This is achieved by organisi
 these files into assigned folders, and using the secureassets module to apply
 security restrictions to those folders.
 
-## Assigning permissions
+## User documentation
 
-To edit permissions for a folder go to the Files section of the cms and select
-the edit icon beside the folder to apply permissions to. The root 'assets'
-folder itself may not be given permissions directly, so only store restricted
-content in a secure subfolder instead.
+ * [Securing file assets](userhelp/index.md)
 
-### Default Folder Permissions
+## Considerations
 
-![Default Folder Permissions](_images/default-permissions.png)
-
-The following permissions are available for every folder:
-
- * `Anyone` - All read - write access is allowed. This is the default value.
- * `Logged-in users` - Only registered users
- * `Only these people` - Allows specific groups to be selected
-
-### Subfolders
-
-![Subfolder Folder Permissions](_images/subfolder-permissions.png)
-
-For folders at the third level or deeper (e.g. assets/Uploads/Subfolder)
-the default value is instead `Inherit`, which will use the same
-permissions as the folder above.
-
-As a matter of best practice it is advisable to avoid giving a folder
-less restrictive permissions than the one above, as users may find
-it difficult to access in the CMS.
-
-### Files
-
-Files will inherit the permissions of the folder they are placed in, but
-may not have permissions assigned directly. This is due to the restriction
-on permissions being placed on a per-folder level.
-
-It is also important to take note when using secure files attached to
-DataObjects which other users may be able to edit. If that user does
-not have permission to view the file attached, then it will not appear
+It is important to take note when using secure files attached to DataObjects which other users may be able to edit. If that user does not have permission to view the file attached, then it will not appear
 against that object, and modification may result in it being detached.
 
-### Pages
-
-Pages may be created in draft with secure files attached, but when this page is
-published you will need to change the permissions on each file to make them accessible.
-
-Try to avoid attaching secure images or other files to live pages (or other DataObjects)
-which may be publicly viewed, to avoid unnecessary access denied errors appearing.
-
-## Other Considerations
-
 Securing files will cause extra load on your webserver and your database,
 as the framework will check the datatabase for access permissions, and pass the
 file data through the framework when it is output to the user.

docs/en/userguide/index.md

@@ -0,0 +1,59 @@
+title: Securing files
+summary: How to secure files inside the Files and Images area
+
+# Securing files
+
+## In this section:
+
+* Assigning folder permissions
+* Permission considerations
+
+## Before we begin:
+
+* Make sure you have the SilverStripe [secure assets](http://addons.silverstripe.org/add-ons/silverstripe/secureassets) module installed
+
+The secure assets module can be used to apply security restrictions to
+the Files and Images area on a folder by folder basis.
+
+## Assigning permissions
+
+To edit permissions for a folder go to the Files section of the cms and select
+the edit icon beside the folder to apply permissions to. The root 'assets'
+folder itself may not be given permissions directly, so only store restricted
+content in a secure subfolder instead.
+
+### Default Folder Permissions
+
+![Default Folder Permissions](_images/default-permissions.png)
+
+The following permissions are available for every folder:
+
+ * `Anyone` - All read - write access is allowed. This is the default value.
+ * `Logged-in users` - Only registered users
+ * `Only these people` - Allows specific groups to be selected
+
+### Subfolders
+
+![Subfolder Folder Permissions](_images/subfolder-permissions.png)
+
+For folders at the third level or deeper (e.g. assets/Uploads/Subfolder)
+the default value is instead `Inherit`, which will use the same
+permissions as the folder above.
+
+<div class="note" markdown='1'>
+As a matter of best practice it is advisable to avoid giving a subfolder
+less restrictive permissions than the one above, as users may find
+it difficult to access in the CMS.
+</div>
+
+## Permission considerations
+
+Files will inherit the permissions of the folder they are placed in, but
+may not have permissions assigned directly. This is due to the restriction
+on permissions being placed on a per-folder level.
+
+Pages may be created in draft with secure files attached, but when this page is
+published you will need to change the permissions on each file to make them accessible.
+
+Try to avoid attaching secure images or other files to live pages (or other DataObjects)
+which may be publicly viewed, to avoid unnecessary access denied errors appearing.