add overriding classes

docs/enhancing-and-overriding/overriding-classes.md

@@ -101,6 +101,6 @@ The definition can be any of the following (from Yii2's DI container):
   the class of the object to be created. If `class` is not specified, `$class` will be used as the class name.
 - a **string**: a class name, an interface name or an alias name.
 
-
-
 > See [how to enhance a User model](how-to-enhance-a-user-model.md) guide to see a practical example.
+
+© [2amigos](http://www.2amigos.us/) 2013-2017

docs/enhancing-and-overriding/overriding-views.md

@@ -0,0 +1,41 @@
+Overriding Views
+================
+
+In case you need to override the default views (that you surely have to do if you use a different them than default's 
+Bootstrap), Yii2 provides a mechanism that is really easy to do: 
+ 
+```php
+// ... other configuration here
+'components' => [
+    'view' => [
+        'theme' => [
+            'pathMap' => [
+                '@Da/User/resources/views' => '@app/views/user'
+            ]
+        ]
+    ]
+]
+// ...
+```
+
+The above code tells Yii2 to search on `@app/view/user` for views prior to go to `@Da/User/resources/views`. That is, 
+if a view is found on `@app/view/user` that matches the required render it will be displayed instead of the one on 
+`@Da/User/resources/views`. 
+
+You need to remember that the folder structure on your new location must match that of the module. For example, if we 
+wish to override the `login.php` view using the above setting, we would have to create the following structure on our 
+path: 
+
+```
+app  [ Your root ]
+|
+└─ views
+    └─ user
+        └─ security
+             login.php
+```
+
+See how it follows the same structure as within the User's module `resources/views` path? Well, that's what you should 
+do with any of the others in order to override them.
+
+© [2amigos](http://www.2amigos.us/) 2013-2017