Migrate pathod docs to Sphinx

All the content of the pathod docs are moved into Sphinx. The interactive
format has not translated well to static docs, and there's still a lot of
rewriting, format fixing, structuring, etc to be done.

1 files changed, 0 insertions, 50 deletions

diff --git a/pathod/templates/docs_test.html b/pathod/templates/docs_test.html
deleted file mode 100644
index ecd84bc7..00000000
--- a/pathod/templates/docs_test.html
+++ /dev/null
@@ -1,50 +0,0 @@
-{% extends "docframe.html" %} {% block body %}
-<div class="page-header">
-    <h1>
-        pathod.test
-        <small>Using pathod in unit tests.</small>
-    </h1>
-</div>
-
-<p>The <b>pathod.test</b> module is a light, flexible testing layer for HTTP clients.
-    It works by firing up a Pathod instance in a separate thread, letting you use
-    Pathod's full abilities to generate responses, and then query Pathod's internal
-    logs to establish what happened. All the mechanics of startup, shutdown, finding
-    free ports and so forth are taken care of for you.
-</p>
-
-<p>The canonical docs can be accessed using pydoc: </p>
-
-<pre class="terminal">pydoc pathod.test</pre>
-
-<p>
-    The remainder of this page demonstrates some common interaction patterns using
-    <a href="http://nose.readthedocs.org/en/latest/">nose</a>. These examples are
-    also applicable with only minor modification to most commonly used Python testing
-    engines.
-</p>
-
-<section>
-    <div class="page-header">
-        <h1>Context Manager</h1>
-    </div>
-
-    {% include "examples_context.html" %}
-</section>
-
-<section>
-    <div class="page-header">
-        <h1>One instance per test</h1>
-    </div>
-
-    {% include "examples_setup.html" %}
-</section>
-
-<section>
-    <div class="page-header">
-        <h1>One instance per suite</h1>
-    </div>
-
-    {% include "examples_setupall.html" %}
-</section>
-{% endblock %}