cleanup document listing - now only worry about writing them

Signed-off-by: Nico Schottelius <nico@brief.schottelius.org>

doc/dev/todo/niconext

@@ -18,6 +18,8 @@
     - cdist-stages.text
     - cdist-type.text
 
+ 51 -> ssh stuff double: cdist-best-practice and here
+
 --------------------------------------------------------------------------------
 
 

doc/man/man7/cdist-tutorial.text

@@ -14,82 +14,76 @@ This document gives you a pointer on what to read in
 which order and is thus more a "guide to the right locations".
 
 cdist-quickstart::
-    Read this, if you are brand new in the cdist world and just want 
-    to get your hands dirty.
-
-cdist-reference::
-    Know everything about cdist: the types, explorers or environment 
-    variables usable.
-
-PARTS BELOW HERE ARE TO-BE-DONE
+    New to cdist? Want to get your hands dirty?  Read this. [beginner]
 
 cdist-installation::
-    The comprehensive guide to your first cdist installation.
+    The comprehensive guide to your first cdist installation [beginner]
 
-cdist-manifest::
-    initial in here
+    - MANAGING YOUR OWN CONFIGURATION
+own branch => very early [before first change?]
+    => no, first quick intro, then do it right
 
-cdist-best-practice::
-cdist-explorer::
-cdist-hacker::
+cdist-initial-manifest::
+    Learn how to define which hosts get which configurations [beginner]
 
-cdist-stages::
 cdist-type::
+    Understand how types are working and created [intermediate]
 
+    CREATING YOUR FIRST OWN TYPE
+    ----------------------------
+    => short example, reference to cdist-type(7)!
+    => motivation
 
+    Use a type to bundle functionalitY
 
--> ssh stuff double: cdist-best-practice and here
+    <with object id? or signleton here already>
 
+    Debug with var - can be used by yourself
+    __debug::
+       If this variable is setup, cdist runs in debug mode.
+       You can use this information, to only output stuff in debug
+       mode as well.
+       Available for: initial manifest, type manifest, gencode, code
 
-CONTINUE READING
-----------------
-So far you have seen how to get cdist up and running and
-how the initial manifest is being used.
-
-own branch => very early [before first change?]
-    => no, first quick intro, then do it right
-It is recommended to 
-- MANAGING YOUR OWN CONFIGURATION
-- write own type
 
+    USING EXPLORERS
+    ---------------
+    cdist-explorer.text
 
-MANAGING YOUR OWN CONFIGURATION
--------------------------------
+    DEBUGGING YOUR TYPES
+    --------------------
 
-CREATING YOUR FIRST OWN TYPE
-----------------------------
-=> short example, reference to cdist-type(7)!
-=> motivation
 
-Use a type to bundle functionalitY
+cdist-best-practice::
+    Hints from real life experience to help you to organise cdist [intermediate]
 
-<with object id? or signleton here already>
+cdist-reference::
+    The type, explorers and environment variables reference [intermediate]
 
-Debug with var - can be used by yourself
-__debug::
-   If this variable is setup, cdist runs in debug mode.
-   You can use this information, to only output stuff in debug
-   mode as well.
-   Available for: initial manifest, type manifest, gencode, code
+cdist-explorer::
+    Interested in getting more information about the target system? [intermediate]
 
+cdist-cache::
+    How to get use information about the hosts we have been working on [advanced]
 
+cdist-scaling-tuning::
+    How to scale out with cdist and which tunings to apply. [advanced]
 
-USING EXPLORERS
----------------
-cdist-explorer.text
+    TUNING CDIST
+    ------------
 
+    - speedup processing with ControlMaster option of
+    ssh
+    => different document
 
-DEBUGGING YOUR TYPES
---------------------
 
+cdist-stages::
+    Understand the internal workflow of cdist. [advanced]
 
+cdist-hacker::
+    README, if you want to extend or modify cdist. [hacker]
 
-TUNING CDIST
-------------
 
-- speedup processing with ControlMaster option of
-ssh
-=> different document
 
 
 SEE ALSO