a bunch of changes to documentation

Author: ErikBjare

architecture.rst

@@ -0,0 +1,50 @@
+============
+Architecture
+============
+
+Here we hope to clarify the architecture of ActivityWatch for you. Please file an issue or pull request if you think something is missing.
+
+Modules
+=======
+
+Server
+------
+
+Known as aw-server, it handles storage and retrieval of all activities/entries in buckets. Usually there exists one bucket per watcher.
+
+Clients
+-------
+
+The server doesn't do anything interesting on its own, for that we need clients such as watchers and user interfaces.
+Writing these  clients is something we've tried to make as easy as possible by creating client libraries with a clear API.
+
+Currently the primary client library is written in Python (known simply as aw-client) but a client library written in JavaScript is on the way and is expected to have the same level of support in the future.
+
+Client libraries:
+
+ - aw-client (Python)
+ - aw-client-js (JavaScript)
+
+Watchers
+^^^^^^^^
+
+Since aw-server doesn't do any data collection on it's own, we need watchers that observe the world and sent the data off to aw-server for storage.
+
+Examples of watchers:
+
+ - aw-watcher-afk
+ - aw-watcher-window
+
+User interfaces
+^^^^^^^^^^^^^^^
+
+Examples of UIs:
+
+ - aw-webui
+
+Libraries
+---------
+
+Some of the logic of ActivityWatch is shared across the server and clients, such as the Event model.
+Due to this, we've created a common library :code:`aw-core` which includes many of the essentials in ActivityWatch.
+

extending.rst

@@ -0,0 +1,33 @@
+Extending ActivityWatch
+=======================
+
+So, you want to do something more with ActivityWatch? Great!
+
+We've tried to make things easy for you (and ourselves) so here's some advice on how to get started.
+
+
+Collecting more data
+--------------------
+
+To do this you'd want to write a so-called watcher. Watchers are small programs that collect data and send it off to the server.
+
+See :doc:`writing-watchers`.
+
+
+Exporting data programatically
+------------------------------
+
+Exporting data is as simple as:
+
+TODO
+
+
+Writing visualizers
+-------------------
+
+Right now, the best way to do this is to simply export the data and transform it yourself to fit the data format you need for your visualization.
+In the future however, we will provide a Python library for common transforms to make things easier for you.
+
+
+
+

features.rst

@@ -0,0 +1,9 @@
+Features
+========
+
+Here we will document a few features.
+
+.. toctree::
+   user-interface
+   pausing-logging
+   filtering-data

index.rst

@@ -8,33 +8,25 @@ Welcome to the ActivityWatch documentation!
 
 .. _user-docs:
 .. toctree::
-   :maxdepth: 2
+   :maxdepth: 3
    :caption: User documentation
 
    introduction
    getting-started
-
-
-.. _feature-docs:
-.. toctree::
-   :maxdepth: 2
-   :caption: Feature documentation
-
-   user-interface
-   pausing-logging
-   filtering-data
+   features
+   extending
 
 
 .. _dev-docs:
 .. toctree::
-   :maxdepth: 2
+   :maxdepth: 3
    :caption: Developer documentation
 
-   api-reference
+   architecture
    installing-from-source
+   api-reference
    development
    writing-watchers
-   modules
    rest