Remove docs/html directory. There is no need to keep the HTML documentation inside the package itself, since it is available on packages.python.org/plone.app.discussion.

svn path=/plone.app.discussion/trunk/; revision=36875

docs/html/architecture.html

@@ -30,9 +30,6 @@
         <li class="right" style="margin-right: 10px">
           <a href="genindex.html" title="General Index"
              accesskey="I">index</a></li>
-        <li class="right" >
-          <a href="modindex.html" title="Global Module Index"
-             accesskey="M">modules</a> |</li>
         <li class="right" >
           <a href="design.html" title="Design Notes"
              accesskey="N">next</a> |</li>
@@ -58,29 +55,29 @@ plone.app.discussion.</p>
 <dd>This makes it easier to search for them and manage them using existing
 CMF and Plone UI constructs.</dd>
 <dt><strong>Discussion items are cataloged</strong></dt>
-<dd>It is be possible to search for discussion items like any other type of
+<dd>It is possible to search for discussion items like any other type of
 content.</dd>
 <dt><strong>Discussion items are subject to workflow and permission</strong></dt>
 <dd>Moderation, anonymous commenting, and auto approve/reject should be
 handled using workflow states, automatic and manual transitions, and
 permissions.</dd>
 <dt><strong>Discussion items are light weight objects</strong></dt>
-<dd>Discussion item objects are as light weight as possible.
-Ideally, a discussion item should be as lightweight as a catalog brain.
-This may mean that we forego convenience base classes and re-implement
-certain interfaces. Comments should not provide the full set of dublin
-core metadata, though custom indexers can be used to provide values for
-standard catalog indexes.</dd>
+<dd>Discussion item objects are as light weight as possible. Ideally, a
+discussion item should be as lightweight as a catalog brain. This may mean
+that we forego convenience base classes and re-implement certain interfaces.
+Comments should not provide the full set of dublin core metadata, though
+custom indexers can be used to provide values for standard catalog indexes.</dd>
 <dt><strong>Optimise for retrival speed</strong></dt>
 <dd>HTML filtering and other processing should happen on save, not on render,
 to make rendering quick.</dd>
 <dt><strong>Settings are stored using plone.registry</strong></dt>
-<dd>Any global setting should be stored in plone.registry records</dd>
+<dd>Any global setting should be stored in plone.registry records.</dd>
 <dt><strong>Forms are constructed using extensible z3c.form forms</strong></dt>
 <dd>This allows plugins (such as spam protection algorithms) to provide
-additional validation</dd>
+additional validation. It also allows integrators to write add-ons that add
+new fields to the comment form.</dd>
 <dt><strong>Discussion items are stored in a BTree container</strong></dt>
-<dd>This allows faster lookup and manipulation</dd>
+<dd>This allows faster lookup and manipulation.</dd>
 <dt><strong>Discussion items are accessed using a dict-like interface</strong></dt>
 <dd>This makes iteration and manipulation more natural. Even if comments are
 not stored threaded, the dict interface should act as if they are, i.e.
@@ -139,9 +136,6 @@ discussion items are added, removed, or modified.</dd>
         <li class="right" style="margin-right: 10px">
           <a href="genindex.html" title="General Index"
              >index</a></li>
-        <li class="right" >
-          <a href="modindex.html" title="Global Module Index"
-             >modules</a> |</li>
         <li class="right" >
           <a href="design.html" title="Design Notes"
              >next</a> |</li>