diff --git a/docs/index.rst b/docs/index.rst
index 62d7badb..c8ad89b2 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -12,6 +12,7 @@ Contents:
    :maxdepth: 2
 
    source/glossary
+   source/resource
    source/orchestration
    source/examples
 
diff --git a/docs/source/glossary.rst b/docs/source/glossary.rst
index ebbea080..1f0581d9 100644
--- a/docs/source/glossary.rst
+++ b/docs/source/glossary.rst
@@ -9,26 +9,14 @@ Solar Glossary
 Resource
 ========
 
+You can learn more about it in :ref:`Resource Details <resource_details>`
+
 .. _res-input-term:
 
 Input
 -----
 Resource configuration that will be used in actions, handlers and orchestration.
-All known inputs should be provided in meta.yaml ::
-
-    input:
-      keystone_password:
-        schema: str!
-        value: 'keystone'
-      keystone_enabled:
-        schema: bool
-        value: true
-      keystone_tenant:
-        schema: str
-        value: 'services'
-      keystone_user:
-        schema: str
-        value: 'cinder'
+All known inputs should be provided in meta.yaml
 
 .. _res-connection-term:
 
@@ -43,16 +31,6 @@ If connection will be removed - original value of child will be preserved.
 Action
 ------
 Solar wraps deployment code into actions with specific names.
-Several actions of resource are mandatory:
-- run
-- remove
-- update
-
-All actions should be provided in meta.yaml ::
-
-    actions:
-      run: run.pp
-      update: run.pp
 
 .. _res-tag-term:
 
@@ -67,10 +45,6 @@ Handler
 =======
 
 Layer that responsible for action execution and tracking result.
-Currently handler specified in resource meta.yaml and used for all resource
-actions ::
-
-  handler: puppet
 
 .. _res-transports-term:
 
diff --git a/docs/source/resource.rst b/docs/source/resource.rst
new file mode 100644
index 00000000..2597dd6c
--- /dev/null
+++ b/docs/source/resource.rst
@@ -0,0 +1,84 @@
+.. _resource_details:
+
+Resource
+========
+
+Resource is one of the key Solar components. Resoruce definition takes place in ``meta.yaml`` file.
+
+
+Basic resource structure
+------------------------
+
+.. code::
+
+   ├── actions
+   │   ├── remove.pp
+   │   ├── run.pp
+   │   └── update.pp
+   └── meta.yaml
+
+
+Handler
+-------
+
+.. TODO: add link to handlers doc there
+
+Layer that is responsible for action execution. You need to specify handler per resource, definition in ``meta.yaml`` looks like ::
+
+  handler: puppet
+
+
+Input
+-----
+Treat them as values that your resouce have. All needed inputs should be provided in ``meta.yaml`` for example ::
+
+  input:
+      keystone_password:
+        schema: str!
+        value: 'keystone'
+      keystone_enabled:
+        schema: bool
+        value: true
+      keystone_tenant:
+        schema: str
+        value: 'services'
+      keystone_user:
+        schema: str
+        value: 'cinder'
+
+Input schema
+~~~~~~~~~~~~
+It allows to validate if all values are correct. ``!`` at the end of a type means that this is required (``null`` value is not valid).
+
+* string type ``str``, ``str!``
+* integer type ``int``, ``int!``
+* boolean type ``bool``, ``bool!``
+* complex types:
+
+  * list of strings ``[str!]``
+  * hash with values ``{a: str!}``
+  * list with hashes ``[{a: str!}]``
+  * list with lists ``[[]]``
+
+
+Action
+------
+Solar wraps deployment code into actions with specific names. Actions are executed by :ref:`res-handler-term`
+
+Several actions of resource are mandatory:
+- run
+- remove
+- update
+
+You can just put files into ``actions`` subdir in your resource or solar will detect them automaticaly, you can also provide actions in ``meta.yaml`` ::
+
+    actions:
+      run: run.pp
+      update: run.pp
+
+Tag
+---
+
+You can attach as many tags to resource as you want, later you can use those tags for grouping etc ::
+
+  tags: [resource=hosts_file, tag_name=tag_value, just_some_label]