reorganize doc TOC, remove old stuff, add links to external documentation
diff --git a/Allura/docs/administration.rst b/Allura/docs/administration.rst
index 19c2e53..303d778 100644
--- a/Allura/docs/administration.rst
+++ b/Allura/docs/administration.rst
@@ -93,3 +93,18 @@
indefinitely (until closed). The notification content can contain HTML. Only the
most recent notification will be shown, unless it has `active:false`, in which case
no notification will be shown.
+
+
+Using Projects and Tools
+------------------------
+
+We currently don't have any further documentation for basic operations of managing
+users, projects, and tools on Allura. However, SourceForge has help docs that cover
+these functions https://sourceforge.net/p/forge/documentation/Docs%20Home/ Note
+that this documentation also covers some SourceForge features that are not part of Allura.
+
+
+Public API Documentation
+------------------------
+
+Allura's web api is currently documented at https://sourceforge.net/p/forge/documentation/Allura%20API/
diff --git a/Allura/docs/index.rst b/Allura/docs/index.rst
index ebbd0bf..81c4426 100644
--- a/Allura/docs/index.rst
+++ b/Allura/docs/index.rst
@@ -20,7 +20,7 @@
You can adapt this file completely to your liking, but it should at least
contain the root `toctree` directive.
-Introducing the *Allura* Platform:
+Introduction
=====================================================================
.. toctree::
@@ -28,7 +28,7 @@
intro
-Getting Started
+Running Allura
=====================================================================
.. toctree::
@@ -36,29 +36,29 @@
installation
administration
- platform_tour
scm_host
migration
-Writing a Allura based app
-=====================================================================
-
-.. toctree::
- :maxdepth: 3
-
- tutorials/wiki-tool
-
-Inside the Platform Components
+Developing Allura
=====================================================================
.. toctree::
:maxdepth: 3
platform
+ platform_tour
guides/message_bus
guides/email
guides/permissions
+
+Extending Allura
+=====================================================================
+
+.. toctree::
+ :maxdepth: 3
+
extending
+ tutorials/tool
API Documentation
==================
@@ -69,19 +69,12 @@
api/*
-Frequently Asked Questions
+Background Info
=====================================================================
.. toctree::
:maxdepth: 1
faq
-
-Project References
-=====================================================================
-
-.. toctree::
- :maxdepth: 1
-
online
Indices and tables
diff --git a/Allura/docs/tutorials/wiki-tool.rst b/Allura/docs/tutorials/tool.rst
similarity index 66%
rename from Allura/docs/tutorials/wiki-tool.rst
rename to Allura/docs/tutorials/tool.rst
index 1e5d4ff..2ab768d 100644
--- a/Allura/docs/tutorials/wiki-tool.rst
+++ b/Allura/docs/tutorials/tool.rst
@@ -18,17 +18,10 @@
Creating your first Allura Tool
=====================================================================
-Adding your Allura Tool to a Allura Install
-=====================================================================
+Tim Van Steenburgh has written a `series of posts guiding you through
+writing an Allura tool <https://sourceforge.net/u/vansteenburgh/allura-plugin-development/>`_.
+There is also a `companion git repo <https://sourceforge.net/u/vansteenburgh/plugin-tutorial/ci/master/tree/>`_.
-Writing a Wiki Tool Part 1: Pages
-=====================================================================
-
-Writing a wiki Tool Part 2: Links
-=====================================================================
-
-Writing a wiki Tool Part 3: Revisions
-=====================================================================
Testing your Tool
===========================
@@ -63,25 +56,3 @@
The framework used to generate the WSGI environment for testing your tools is
provided by the `WebTest <http://pythonpaste.org/webtest/>`_ module, where you can
find further documentation for the `.get()` and `.post()` methods.
-
-Testing Allura models is also straightforward, though it usually requires
-setting the pylons context object `c` before your test. An example of this
-technique follows::
-
- import mock
- from pylons import tmpl_context as c, app_globals as g
-
- from allura.lib.app_globals import Globals
- from allura import model as M
-
- def setUp():
- g._push_object(Globals())
- c._push_object(mock.Mock())
- g.set_project('projects/test')
- g.set_app('hello')
- c.user = M.User.query.get(username='test-admin')
-
-Testing the tasks and events is similar to testing models. Generally, you will
-simply want to call your `@task` and `@event_handler` methods directly rather
-than setting up a full mocking infrastructure, though it is possible to use the
-MonQTask model in the allura model if you wish to do more functional/integration testing.
