Organize the developer docs into a "Pilcrow for Developers" book.

The audience for this is developers looking to make changes to Pilcrow, either on the server, on the included client, or via its data model. Most of the material here is drawn from existing documents, but organized somewhat more coherently.

I've left some space for client documentation, though no such documents exist yet.

1 files changed, 9 insertions, 0 deletions

diff --git a/tools/docs-developer b/tools/docs-developer
new file mode 100755
index 0000000..bb042d1
--- /dev/null
+++ b/tools/docs-developer
@@ -0,0 +1,9 @@
+#!/bin/bash -e
+
+## tools/docs-developer
+##
+## Builds (and opens) the developer documentation.
+
+cd "$(dirname "$0")/.."
+
+mdbook serve --open docs/developer