diff --git a/.gitignore b/.gitignore
index 7b70f42..835ee8f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -31,3 +31,5 @@ dist/
venv/
.tox/
.docker/
+docs_sphinx/venv/
+docs_sphinx/build/
diff --git a/docs/JSON.md b/docs/JSON.md
new file mode 100644
index 0000000..8338249
--- /dev/null
+++ b/docs/JSON.md
@@ -0,0 +1,125 @@
+
+# JSON Data Source
+
+> **Tip**
+> See [examples/](../examples/) for sample configuration files.
+
+## Overview
+
+`JsonImporter` reads benchmark results from a local JSON file and feeds them into Otava for change-point analysis. It is a simple data source to set up — no external database or service is required.
+
+The importer caches parsed file content in memory, so a file is only read once per session even if multiple tests reference the same path.
+
+---
+
+## Expected JSON Format
+
+The input file must be a JSON array. Each element represents a single benchmark run.
+```json
+[
+ {
+ "timestamp": 1711929600,
+ "metrics": [
+ { "name": "throughput", "value": 4821.0 },
+ { "name": "p99_latency_ms", "value": 142.7 }
+ ],
+ "attributes": {
+ "branch": "main",
+ "commit": "a3f9c12"
+ }
+ },
+ {
+ "timestamp": 1712016000,
+ "metrics": [
+ { "name": "throughput", "value": 5013.0 },
+ { "name": "p99_latency_ms", "value": 138.2 }
+ ],
+ "attributes": {
+ "branch": "main",
+ "commit": "b7d2e45"
+ }
+ }
+]
+```
+
+---
+
+## Fields
+
+### `timestamp`
+
+- **Type:** integer (Unix epoch seconds)
+- **Required:** yes
+- Identifies when the commit was merged into the tracked branch. This timestamp should remain constant for the same commit, even if benchmarks are rerun multiple times.
+
+### `metrics`
+
+- **Type:** array of objects
+- **Required:** yes
+- Each object must have:
+ - `name` (string) — unique identifier for the metric within this result
+ - `value` (number) — the measured value
+- Metric names must be consistent across results for change-point analysis to be meaningful.
+
+> Note: A `unit` field (e.g., "ms") is not currently supported by JsonImporter.
+
+### `attributes`
+
+- **Type:** object (string → string)
+- **Required:** no
+- Arbitrary key-value pairs describing the run context (e.g. branch, commit, version).
+- The `branch` key is required only when using branch-based filtering.
+---
+
+## Configuration Example
+
+Add a test with `type: json` to your `otava.yaml`:
+```yaml
+tests:
+ my_benchmark:
+ type: json
+ file: otava/examples/json/data/sample.json
+ base_branch: main
+```
+
+| Field | Required | Description |
+|---|---|---|
+| `type` | yes | Must be `json` |
+| `file` | yes | Path to the JSON file |
+| `base_branch` | no | If set, only runs from this branch are analyzed by default |
+
+---
+
+## Limitations
+
+- The entire file is read into memory at once. Very large files may cause high memory usage.
+- There is no schema validation. Missing or malformed fields will cause a `KeyError` at runtime.
+- The `branch` filter requires the key `"branch"` to exist inside `attributes` on every entry — if it is absent on any entry that would otherwise be included, the importer will raise a `KeyError`.
+- Attribute values are expected to be strings. No type coercion is performed.
+- The file path is resolved at config load time; a missing file raises a `TestConfigError` immediately.
+
+---
+
+## Example Usage
+
+Analyze test results stored in JSON format:
+```bash
+otava analyze my_benchmark --config otava/examples/json/config/otava.yaml
+```
diff --git a/docs/index.html b/docs/index.html
new file mode 100644
index 0000000..7c8201e
--- /dev/null
+++ b/docs/index.html
@@ -0,0 +1,100 @@
+
+
+
+
+
+ Apache Otava Documentation
+
+
+
+
+
+
+
+
Apache Otava Documentation
+
+
+ Structured entry point to the Otava documentation, replacing the default directory listing.
+
+
+
+
+
+
+