Jon Pretty

common problem: published doc for past release is immutable

amok is a database of Metadatas (organized in trees linked to a git commit) that can be queried, a linkers for urls that can merge sparse trees together and build the doc. All in an universal namespace => several amok repo can be merged together

current status: db works for simple case (branches, merges). Not for squash/rebase (b/c change hashes). Problem can be tooled away only if doc and code are managed together (git hook, etc). When you don't own the code repo: no idea for now ("be careful")

I forget to talk about the presentation layer. Current status: rendering raw, html, markdown... It works by recursively fetch content from amok.