Convert the API URL system from an App based one

to a resource based one.

Signed-off-by: Roberto Rosario <roberto.rosario.gonzalez@gmail.com>

docs/releases/3.0.rst

@@ -71,7 +71,8 @@ Backward incompatible changes
 Bugs fixed or issues closed
 ===========================
 
-* `GitLab issue #378 <https://gitlab.com/mayan-edms/mayan-edms/issues/378>`_ Add metadata widget changes from @Macrobb
+* `GitLab issue #366 <https://gitlab.com/mayan-edms/mayan-edms/issues/366>`_ Proofread documentation
+* `GitLab issue #379 <https://gitlab.com/mayan-edms/mayan-edms/issues/379>`_ Add new document version list view permission.
 * `GitLab issue #379 <https://gitlab.com/mayan-edms/mayan-edms/issues/379>`_ Add new document version list view permission.
 
 

docs/topics/deploying.rst

@@ -3,7 +3,8 @@ Advanced deployment
 ===================
 
 Mayan EDMS should be deployed like any other Django_ project and
-preferably using virtualenv_.
+preferably using virtualenv_. Below are some ways to deploy and use Mayan EDMS.
+Do not use more than one method.
 
 Being a Django_ and a Python_ project, familiarity with these technologies is
 recommended to better understand why Mayan EDMS does some of the things it
@@ -58,7 +59,7 @@ to /usr/bin/ with ...
 
     sudo ln -s /opt/local/bin/tesseract /usr/bin/tesseract
 
-... alternatively set the paths in the ``settings/locals.py``
+Alternatively, set the paths in the ``settings/locals.py``
 
 .. code-block:: python
 
@@ -76,9 +77,9 @@ With Homebrew installed run the command:
 Set the Binary paths
 ********************
 
-Mayan EDMS by default will look in /usr/bin/ for the binary files it needs
-so either you can symlink the binaries installed via brew in /usr/local/bin/
-to /usr/bin/ with ...
+Mayan EDMS by default will look in /usr/bin/ for the binary files it needs.
+You can symlink the binaries installed via brew in /usr/local/bin/
+to /usr/bin/ with:
 
 .. code-block:: bash
 
@@ -87,7 +88,7 @@ to /usr/bin/ with ...
     sudo ln -s /usr/local/bin/pdftotext /usr/bin/pdftotext && \
     sudo ln -s /usr/local/bin/gs /usr/bin/gs
 
-... alternatively set the paths in the ``settings/locals.py``
+Alternatively, set the paths in the ``settings/locals.py``
 
 .. code-block:: python
 
@@ -265,15 +266,18 @@ Make the installation directory readable and writable by the webserver user::
 
     chown www-data:www-data /usr/share/mayan-edms -R
 
-Restart the services::
+Enable and restart the services [1_]::
 
     systemctl enable supervisor
     systemctl restart supervisor
     systemctl restart nginx
 
+[1]: https://bugs.launchpad.net/ubuntu/+source/supervisor/+bug/1594740
+
 .. _Debian: http://www.debian.org/
 .. _Django: http://www.djangoproject.com/
 .. _Python: http://www.python.org/
 .. _SQLite: https://www.sqlite.org/
 .. _Ubuntu: http://www.ubuntu.com/
 .. _virtualenv: http://www.virtualenv.org/en/latest/index.html
+.. _1: https://bugs.launchpad.net/ubuntu/+source/supervisor/+bug/1594740

docs/topics/development.rst

@@ -16,8 +16,8 @@ request on GitLab_.
 Project philosophies
 --------------------
 
-How to think about Mayan EDMS when doing changes or adding new features,
-why things are the way they are in Mayan EDMS.
+How to think about Mayan EDMS when doing changes or adding new features;
+why things are the way they are in Mayan EDMS:
 
 - Functionality must be as market/sector independent as possible, code for the
   95% of use cases.
@@ -36,7 +36,7 @@ why things are the way they are in Mayan EDMS.
   not viable/mature/efficient.
 - Each app is as independent and self contained as possible. Exceptions, the
   basic requirements: navigation, permissions, common, main.
-- If an app is meant to be used by more than one other app it should be as
+- If an app is meant to be used by more than one other app, it should be as
   generic as possible in regard to the project and another app will bridge the functionality.
 
   - Example: since indexing (document_indexing) only applies to documents, the
@@ -48,7 +48,7 @@ Coding conventions
 
 Follow PEP8
 ~~~~~~~~~~~
-Whenever possible, but don't obsess over things like line length.
+Whenever possible, but don't obsess over things like line length:
 
 .. code-block:: bash
 
@@ -103,9 +103,9 @@ Example:
     )
     from .models import Index, IndexInstanceNode, DocumentRenameCount
 
-All local app module imports are in relative form, local app module name is to
+All local app module imports are in relative form. Local app module name is to
 be referenced as little as possible, unless required by a specific feature,
-trick, restriction, ie: Runtime modification of the module's attributes.
+trick, restriction (e.g., Runtime modification of the module's attributes).
 
 Incorrect:
 
@@ -128,7 +128,7 @@ Dependencies
 Mayan EDMS apps follow a hierarchical model of dependency. Apps import from
 their parents or siblings, never from their children. Think plugins. A parent
 app must never assume anything about a possible existing child app. The
-documents app and the Document model are the basic entities they must never
+documents app and the Document model are the basic entities; they must never
 import anything else. The common and main apps are the base apps.
 
 

docs/topics/features.rst

@@ -30,7 +30,7 @@ Features
 * Dynamic default values for metadata.
 
   * Metadata fields can have an initial value, which can be static or determined
-    by an user provided template code snippet.
+    by a template code snippet provided by the user.
 
 * Documents can be uploaded from different sources.
 
@@ -68,7 +68,7 @@ Features
 
 * Multi page document support.
 
-  * Multiple page PDFs and TIFFs files are supported.
+  * Multiple page PDF and TIFF files are supported.
 
 * Automatic OCR processing.
 

docs/topics/transformations.rst

@@ -2,21 +2,20 @@
 Transformations
 ===============
 
-Transformation are persistent manipulations to the previews of the stored
-documents. For example: a scanning equipment may only produce landscape PDFs.
-In this case an useful transformation for that document source would be to
-rotate all documents scanned by 270 degrees after being uploaded, this way
-whenever a document is uploaded from that scanner it will appear in portrait
-orientation. In this case add a this transformation to the Mayan EDMS source
-that is connected to that device this way all pages scanned via that source
-with inherit the transformation as they are created.
+Transformations are persistent manipulations to the previews of the stored 
+documents. For example: a scanning equipment may only produce landscape PDFs. 
+In this case a useful transformation for that document source would be to rotate 
+all scanned documents by 270 degrees after being uploaded. By adding this 
+transformation to the Mayan EDMS source that is connected to the scanner, all 
+pages scanned via that source will inherit the transformation as they are 
+created. The result is that whenever a document is uploaded from that scanner, 
+it will appear in portrait orientation, instead of landscape orientation.
 
-Transformations can also be added to existing documents, by clicking on a
-document's page, then clicking on "transformations". In this view the Actions
-menu will have a new option that reads "Create new transformation". At the
-moment the rotation, zoom, crop, and resize transformations are available.
-Once the document image has been corrected resubmit it for OCR for improved
-results.
+Transformations can also be added to existing documents by clicking on a
+document's page and then clicking on "transformations". In this view the Actions 
+menu will have a new option that reads "Create new transformation". Currently, 
+the available transformations are: rotation, zoom, crop, and resize. Once the 
+document image has been corrected, resubmit it for OCR for improved results.
 
-Transformations are not destructive and do not physically modify the document
+Transformations are not destructive and do not physically modify the document 
 file, they just modify the document's graphical representation.