Mention resources.

1 files changed, 14 insertions, 6 deletions

diff --git a/docs/tutorials/cmf/skins.rst b/docs/tutorials/cmf/skins.rst
index ab9bb5cb1..549fb4621 100644
--- a/docs/tutorials/cmf/skins.rst
+++ b/docs/tutorials/cmf/skins.rst
@@ -11,12 +11,20 @@ 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
+To override static resources using a "search path" much like a set of
+skin layers, :mod:`repoze.bfg` provides the concept of
+:term:`resource` overrides.  See :ref:`overriding_resources_section`
+for more information about resource overrides.
+
+While there is no analogue to a skin layer search path for locating
+Python code (as opposed to resources), :term:`view` code combined with
 differing :term:`request type` attributes can provide a good deal of
-the same sort of behavior.  The `repoze.bfg.skins
-<http://svn.repoze.org/repoze.bfg.skins/>`_ 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.
+the same sort of behavior.  See
+:ref:`using_an_event_to_vary_the_request_type` for more information.
+
+Relatedly, the `repoze.bfg.skins
+<http://svn.repoze.org/repoze.bfg.skins/>`_ package is an attempt to
+allow directories on disk to represent collections of views simply by
+adding templates to the directory.