Add repository descriptions from Rich Bowens PR (#14)
diff --git a/content/docs/downloads.html b/content/docs/downloads.html
index 97e23a7..fae4fbc 100644
--- a/content/docs/downloads.html
+++ b/content/docs/downloads.html
@@ -32,10 +32,30 @@
<h3 id='sourcerepositories'>Source repositories<a href='#sourcerepositories' style='color: rgba(0,0,0,0);'>¶</a></h3>
<p>Our source repositories are available on GitHub:</p>
<p><a href="https://github.com/apache/kibble-1">Kibble-1 Main Server/UI</a></p>
+<p>This is the main server and UI for Kibble. It consists of four parts parts:</p>
+<ul>
+<li>A database (ElasticSearch)</li>
+<li>An OpenAPI-driven WSGI interface for displaying pages and operating
+the JSON API (as well as printing the API docs).</li>
+<li>A user interface for managing the database, user accounts and
+requesting visualizations</li>
+<li>A visualization library for displaying all the various charts.</p>
+Everything backend in Kibble is using Python 3. Everything frontend is
+using CoffeeScript transpiled to JavaScript.</li>
+</ul>
<p><a href="https://github.com/apache/kibble-scanners">Kibble-1 Scanner Applications</a></p>
+<p>The kibble-scanners repository contains the scanning applications that gather
+data for the main server.</p>
+<ul>
+<li>They are essentially tiny plugins managed by a main application (kibble-scanner.py) and gather what they figure they can find about a data source.</li>
+<li>They connect to the master server, fetch a list of data sources to analyse, and then each plugin decides whether it wants to work with that source, sorted by a run-order (so that fetching a git repository happens before analysing it etc).</li>
+<li>They then collect and formalize data objects, which can be an email, a commit, a person, an issue etc, and pass all that back to the main server's database.</li>
+</ul>
<p><a href="https://github.com/apache/kibble-website">Kibble Web Site</a></p>
-<p><strong>NOTE:</strong> We are currently working on a roadmap to redesign and re-write Kibble so the current Kibble repository is a work in progress (WIP).The Kibble-1 repositories contain the code used for our demo.</p>
-<p><a href="https://github.com/apache/kibble-1">Kibble WIP</a></p>
+<p>This is our project web site. It uses the generate.py in the src folder
+to generate html from the markdown source. See BUILDING.txt there.</p>
+<p><a href="https://github.com/apache/kibble">Kibble - the next generation is WIP</a></p>
+<p>We are currently working on a roadmap to redesign and re-write Kibble so the current Kibble repository is a work in progress (WIP).The Kibble-1 repositories mentioned above contain the code used for our website demo.</p>
<h3 id='releases'>Releases<a href='#releases' style='color: rgba(0,0,0,0);'>¶</a></h3>
<p>Nothing available yet, sorry!</p></div>
</div>
diff --git a/source/markdown/docs/downloads.md b/source/markdown/docs/downloads.md
index 50db285..19b3c15 100644
--- a/source/markdown/docs/downloads.md
+++ b/source/markdown/docs/downloads.md
@@ -6,13 +6,34 @@
[Kibble-1 Main Server/UI](https://github.com/apache/kibble-1)
+This is the main server and UI for Kibble. It consists of four parts parts:
+
+- A database (ElasticSearch)
+- An OpenAPI-driven WSGI interface for displaying pages and operating
+the JSON API (as well as printing the API docs).
+- A user interface for managing the database, user accounts and
+requesting visualizations
+- A visualization library for displaying all the various charts.</p>
+Everything backend in Kibble is using Python 3. Everything frontend is
+using CoffeeScript transpiled to JavaScript.
+
[Kibble-1 Scanner Applications](https://github.com/apache/kibble-scanners)
+The kibble-scanners repository contains the scanning applications that gather
+data for the main server.
+
+- They are essentially tiny plugins managed by a main application (kibble-scanner.py) and gather what they figure they can find about a data source.
+- They connect to the master server, fetch a list of data sources to analyse, and then each plugin decides whether it wants to work with that source, sorted by a run-order (so that fetching a git repository happens before analysing it etc).
+- They then collect and formalize data objects, which can be an email, a commit, a person, an issue etc, and pass all that back to the main server's database.
+
[Kibble Web Site](https://github.com/apache/kibble-website)
-**NOTE:** We are currently working on a roadmap to redesign and re-write Kibble so the current Kibble repository is a work in progress (WIP).The Kibble-1 repositories contain the code used for our demo.
+This is our project web site. It uses the generate.py in the src folder
+to generate html from the markdown source. See BUILDING.txt there.
-[Kibble WIP](https://github.com/apache/kibble-1)
+[Kibble - the next generation is WIP](https://github.com/apache/kibble)
+
+We are currently working on a roadmap to redesign and re-write Kibble so the current Kibble repository is a work in progress (WIP).The Kibble-1 repositories mentioned above contain the code used for our website demo.
### Releases
Nothing available yet, sorry!
