Add skins chapter.

2 files changed, 24 insertions, 1 deletions

diff --git a/docs/tutorials/cmf/index.rst b/docs/tutorials/cmf/index.rst
index b3ece7f0e..fd393e3b0 100644
--- a/docs/tutorials/cmf/index.rst
+++ b/docs/tutorials/cmf/index.rst
@@ -12,7 +12,6 @@ Missing:
    templates.rst
    forms.rst
    workflow.rst
-   skins.rst
    actions.rst
    membership.rst
    discussions.rst
@@ -24,4 +23,6 @@ Missing:
 
    content.rst
    catalog.rst
+   skins.rst
+
 
diff --git a/docs/tutorials/cmf/skins.rst b/docs/tutorials/cmf/skins.rst
new file mode 100644
index 000000000..2e444c4db
--- /dev/null
+++ b/docs/tutorials/cmf/skins.rst
@@ -0,0 +1,22 @@
+.. _skins_chapter:
+
+=====
+Skins
+=====
+
+In CMF, a "skin layer" is defined as a collection of templates and
+code (Python scripts, DTML methods, etc) that can be activated and
+deactivated within a particular setup.  A collection of active "skin
+layers" grouped in a particular order forms a "skin".  "Add-on" CMF
+products often provide skin layers that are activated within a
+particular skin to provide the site with additional features.
+
+:mod:`repoze.bfg` itself has no such concept, and no package provides
+a direct replacement, but bfg :term:`view` code combined with
+differing :term:`request type` attributes can provide a good deal of
+the same sort of behavior.  The `vudo.bfg <http://docs.vudo.me/>`_
+package is an attempt to allow directories on disk to represent
+collections of templates, each of which can be thought of as a minimal
+skin.
+
+