diff --git a/docs/config.rst b/docs/config.rst
index cac1d81..1affc01 100644
--- a/docs/config.rst
+++ b/docs/config.rst
@@ -443,6 +443,21 @@ values. The valid configuration keys are listed below.
         removed some tiles, you may need to do some manual deletion on the
         remote side.
 
+.. _option_markers:
+
+``markers``
+    This controls the display of markers, signs, and other points of interest
+    in the output HTML.  It should be a list of filter functions.  
+
+    .. note::
+
+       Setting this configuration option alone does nothing.  In order to get
+       markers and signs on our map, you must also run the genPO script.  See
+       the :doc:`Signs and markers<signs>` section for more details and documenation.
+
+    
+    **Default:** ``[]`` (an empty list)
+
 .. _customrendermodes:
 
 Custom Rendermodes and Rendermode Primitives
diff --git a/docs/index.rst b/docs/index.rst
index 2447f22..5bbac6d 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -181,6 +181,7 @@ Documentation Contents
    building
    running
    config
+   signs
    win_tut/windowsguide
    faq
    design/designdoc
diff --git a/docs/signs.rst b/docs/signs.rst
new file mode 100644
index 0000000..1a2177f
--- /dev/null
+++ b/docs/signs.rst
@@ -0,0 +1,75 @@
+.. _signsmarkers:
+
+=================
+Signs and Markers
+=================
+
+The Overviewer can display signs, markers, and other points of interest on your
+map.  This works a little differently than it has in the past, so be sure to read
+these docs carefully.
+
+In these docs, we use the term POI (or point of interest) to refer to entities and
+tileentities.
+
+
+Configuration File
+==================
+
+
+Filter Functions
+----------------
+
+A filter function is a python function that is used to figure out if a given POI
+should be part of a markerSet of not.  The function should accept one argument
+(a dictionary, also know as an associative array), and return a boolean::
+
+    def signFilter(poi):
+        "All signs"
+        return poi['id'] == 'Sign'
+
+The single argument will either a TileEntity, or an Entity taken directly from 
+the chunk file.  In this example, this function returns true only if the type
+of entity is a sign.  For more information of TileEntities and Entities, see
+the `Chunk Format <http://www.minecraftwiki.net/wiki/Chunk_format>`_ page on
+the Minecraft Wiki.
+
+.. note::
+   The doc string ("All signs" in this example) is important.  It is the label
+   that appears in your rendered map
+
+A more advanced filter may also look at other entity fields, such as the sign text::
+
+    def goldFilter(poi):
+        "Gold"
+        return poi['id'] == 'Sign' and (\
+            'gold' in poi['Text1] or
+            'gold' in poi['Text2'])
+           
+This looks for the word 'gold' in either the first or second line of the signtext.
+
+Since writing these filters can be a little tedious, a set of predefined filters
+functions are provided.  See the :ref:`predefined_filter_functions` section for
+details.
+
+Render Dictionary Key
+---------------------
+
+Each render can specify a list of zero or more filter functions.  Each of these
+filter functions become a selectable item in the 'Signs' drop-down menu in the
+rendered map.  For example::
+
+    renders['myrender'] = {
+            'world': 'myworld',
+            'title': "Example",
+            'markers': [allFilter, anotherFilter],
+    }
+
+
+
+.. _predefined_filter_functions:
+
+Predefined Filter Functions
+===========================
+
+TODO write some filter functions, then document them here
+