A major overhaul of our in-blend naming conventions.

Goals:
- Every asset datablock must have a unique name to avoid Override issues
- Separators could be more consistent and meaningful
- No unnecessary strictness, eg. for Pose Library

@@ -8,2 +10,3 @@
 
-We use prefixes only for top level collections of an asset. This is important to distinguish types of assets. The name of the asset itself should be lowercase.
+All local datablocks across all assets of a production must have a unique name. To faciliate this, each asset is assigned a mnemonic that must remain unique within a given production. For example, a character named "Elder Sprite" might get the mnemonic "ES". The max length of this mnemonic is not limited, but the shorter the better. If a minor prop in the production is called "Electric Switch", it can not have the mnemonic "ES", because it's already taken. So, "ELSW" would be fine. 
+

@@ -22,3 +54,3 @@
 
-All objects should have a prefix, followed by a dash that determines their type:
+It is advisable to give Objects an additional prefix to provide information about the object's purpose, especially when it is NOT part of an asset. This is purely for organizational and comfort purposes. Here are some recommendations:
 

@@ -36,2 +69,3 @@
+Example: `GEO-WRDB-drawer_knob.L` for the left-side drawer knob of a wardrobe prop.
 
-If a name contains a *of* relationship - in the above example the `drawer` of the `dresser` - these should not be separated by a dot, but rather with an underscore.
+If a name contains an "*of*" relationship - in the above example the `knob` *of* the `drawer` - these should NOT be separated by `.`, but rather with `_`.

@@ -51,1 +91,3 @@
-- `ANI` Animation to be used in a shot
+Examples:
+```
+Hand_Fist

@@ -6,0 +3,4 @@
+## Separators
+We only have 3 separators to work with, so we try keep their meaning consistent across conventions:  
+`-` : Separates prefixes from each other and from the rest of the name.  
+`_` : Used instead of spacebar in composite words, eg. `eifel_tower_base`.  

@@ -6,0 +4,4 @@
+We only have 3 separators to work with, so we try keep their meaning consistent across conventions:  
+`-` : Separates prefixes from each other and from the rest of the name.  
+`_` : Used instead of spacebar in composite words, eg. `eifel_tower_base`.  
+`.` : Suffixes, used only for symmetry sides, ie `.L`/`.R`, and for variations, `clock.normal`, `clock.broken`, `clock.destroyed`  

@@ -6,2 +7,3 @@
+`.` : Suffixes, used only for symmetry sides, ie `.L`/`.R`, and for variations, `clock.normal`, `clock.broken`, `clock.destroyed`  
 
-## Collection names
+## Asset Mnemonic

@@ -16,2 +28,3 @@
+Note that there's no technical distinction between different types of assets. This is purely for organizational purposes and comfort.
 
-Example: `CH-phileas`
+The immediate sub-collections of the root collection are strictly defined by our Asset Pipeline add-on, as being `{mnemonic}-{task_layer}`. Task Layers are the different data layers that make up an asset, such as Modeling, Rigging, and Shading. Inside these Task Layer Collections, each artist responsible for their own Task Layer may create sub-collections freely, as long as each sub-collection still starts with `{mnemonic}-{task_layer}-`.

@@ -18,0 +31,4 @@
+So, here's what an asset's collection hierarchy might look like:
+```txt
+CH-elder_sprite
+    ES-model

@@ -32,0 +75,4 @@
+For complex assets, try to use dashes to indicate a nested hierarchy of objects, eg:
+```
+PR-wardrobe
+    wardrobe.model