diff --git a/Resources/doc/basic-usage.rst b/Resources/doc/basic-usage.rst
new file mode 100644
index 000000000..69645d886
--- /dev/null
+++ b/Resources/doc/basic-usage.rst
@@ -0,0 +1,94 @@
+Basic Usage
+===========
+
+This bundle works by configuring a set of filters and then applying those
+filters to images inside a template So, start by creating some sort of filter
+that you need to apply somewhere in your application. For example, suppose
+you want to thumbnail an image to a size of 120x90 pixels:
+
+.. code-block:: yaml
+
+    # app/config/config.yml
+
+    liip_imagine:
+        resolvers:
+           default:
+              web_path: ~
+
+        filter_sets:
+            cache: ~
+            my_thumb:
+                quality: 75
+                filters:
+                    thumbnail: { size: [120, 90], mode: outbound }
+
+You've now defined a filter set called `my_thumb` that performs a thumbnail transformation.
+We'll learn more about available transformations later, but for now, this
+new filter can be used immediately in a template:
+
+.. code-block:: jinja
+
+    <img src="{{ '/relative/path/to/image.jpg' | imagine_filter('my_thumb') }}" />
+
+Or if you're using PHP templates:
+
+.. code-block:: php
+    
+    <img src="<?php $this['imagine']->filter('/relative/path/to/image.jpg', 'my_thumb') ?>" />
+
+Behind the scenes, the bundles applies the filter(s) to the image on the first
+request and then caches the image to a similar path. On the next request,
+the cached image would be served directly from the file system.
+
+In this example, the final rendered path would be something like
+`/media/cache/my_thumb/relative/path/to/image.jpg`. This is where Imagine
+would save the filtered image file.
+
+You can also pass some options at runtime:
+
+.. code-block:: jinja
+
+    {% set runtimeConfig = {"thumbnail": {"size": [50, 50] }} %}
+    <img src="{{ '/relative/path/to/image.jpg' | imagine_filter('my_thumb', runtimeConfig) }}" />
+
+Or if you're using PHP templates:
+
+.. code-block:: php
+
+    <?php
+    $runtimeConfig = array(
+        "thumbnail" => array(
+            "size" => array(50, 50)
+        )
+    );
+    ?>
+
+    <img src="<?php $this['imagine']->filter('/relative/path/to/image.jpg', 'my_thumb', $runtimeConfig) ?>" />
+
+Also you can resolve image url from console:
+
+.. code-block:: jinja
+
+    app/console liip:imagine:cache:resolve relative/path/to/image.jpg relative/path/to/image2.jpg --filters=my_thumb --filters=thumbnail_default
+
+Where only paths required parameter. They are separated by space. If you omit filters option will be applied all available filters.
+
+If you need to access filtered image URL in your controller:
+
+.. code-block:: php
+    
+    $this->get('liip_imagine.cache.manager')->getBrowserPath('/relative/path/to/image.jpg', 'my_thumb', true),
+
+In this case, the final rendered path would contain some random data in the path
+`/media/cache/my_thumb/S8rrlhhQ/relative/path/to/image.jpg`. This is where Imagine
+would save the filtered image file.
+
+.. note::
+    Using the ``dev`` environment you might find that the images are not properly rendered when
+    using the template helper. This is likely caused by having ``intercept_redirect`` enabled in your
+    application configuration. To ensure that the images are rendered disable this option:
+
+    .. code-block:: jinja
+        
+        web_profiler:
+            intercept_redirects: false
diff --git a/Resources/doc/index.rst b/Resources/doc/index.rst
index 347d6e0ea..4e5d65a51 100644
--- a/Resources/doc/index.rst
+++ b/Resources/doc/index.rst
@@ -7,6 +7,7 @@ performance, altered images can be cached locally and in Amazon S3 service.
 
 * :doc:`Installation <installation>`
 * :doc:`Introduction <introduction>`
+* :doc:`Basic usage <basic-usage>`
 * :doc:`Configuration <configuration>`
 * :doc:`Filters <filters>`
 * :doc:`DataLoaders <data-loaders>`